Fernando Fiori

Hi, just an update on the feature: - implementation is complete, tracking bug: https://issues.chromium.org/issues/365046212 - TAG review in progress here: https://github.com/w3ctag/design-reviews/issues/1043 - Spec was written here: https://drafts.csswg.org/css-highlight-api-1/#interactions Let me know...

Hi, just wanted to know if there's any news on this topic. As an update on the API, the return type has been expanded to include the ranges hit for...

Thanks @dandclark! @annevk could you PTAL? Or let me know who else could review this? I don't have permissions to add reviewers.

@annevk friendly ping on this PR, I'd appreciate if you could take a look when you have some time :)

@domenic thanks for having a look! I've been reading all the old discussions, let me see if I'm misunderstanding the intended behavior: Let's say we have top-level frame A, hosting...

@domenic thanks for your comments! I'll reply inline. > I'm not sure. It depends on the original intent of the proposal. If it was to prevent malicious third-party frames from...

> However, my larger point stands, even with an allowlist approach: > > That is not how any other permission policy works, e.g., if evil.example is denied from using WebUSB,...

To expand on this: > Do you know of specific sites that need these changes to the current policy? Besides the example for the To Do app in Outlook I...

@annevk, thanks for your comments so far. I'd like to make sure we're on the same page about behaviors before continuing the discussion on the technical details of the spec....

I'm back :) Thanks @ydogandjiev for summarizing the context, and thanks @smaug---- for your interest in the policy. Regarding the fullscreen case you mentioned: if the user triggers fullscreen on...