Hi, from a privacy perspective we have some concerns regarding the
spellchecker section: we enforced in the past the concept that websites
should not learn about the user dictionaries [1] and it seems like the
spellcheking API proposal could leak those via the *textformatupdate *event.
Was
t, I'm working closely with at least one quick
> adopter, and the quick agreement in the WebRTC Working Group shows this is
> generally useful and a part of the roadmap.
>
> Thanks!
>
> On Mon, 8 May 2023 at 16:21, Nicola Tommasi wrote:
>
>> Hi Tony,
>>
>>
Hi Tony,
Thanks for this intent, could you please clarify why this new field is
needed and important?Without an explainer is hard to follow this change.
Cheers,
Nicola
On Tuesday, May 2, 2023 at 2:29:22 PM UTC Tony Herre wrote:
> Contact emails
>
> he...@google.com, gui...@chromium.com
>
>
:
> On Fri, Mar 24, 2023 at 2:45 AM Nicola Tommasi
> wrote:
>
>> Hi Adam,
>>
>> Thanks for sending this intent. I'm trying to understand a bit more the
>> proposed deprecation so I have a few questions for you:
>>
>> - Are these URIs already used by other API
Hi Adam,
Thanks for sending this intent. I'm trying to understand a bit more the
proposed deprecation so I have a few questions for you:
- Are these URIs already used by other APIs?If so, could you please make an
example?
- Do you plan to block these URIs only for the mdoc presentation API?If
e intended for the newer
>> shape - i.e. renderer SET.
>>
>> Please let me know if we can provide any more details.
>>
>> Hannah
>>
>>
>>
>>
>>
>> On Mon, Jun 13, 2022 at 7:16 AM Nicola Tommasi
>> wrote:
>>
>>
Hi API owners,
This intent seems to be already approved in the past for same-origin
experimentation, is this launch intended for the cross-origin case?If not,
what's exactly in the scope for this particular launch?
Thanks,
Nicola
On Thursday, June 9, 2022 at 8:35:23 AM UTC Yoav Weiss wrote:
