Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

Hi Dan, for your concern that Firefox is still failing the WPTs at https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html, that might be another issue. Let me make more explanation. Actually, the final goal of w3c modifys the spec of selectionchange event is to

Re: [blink-dev] Intent to Experiment: Keyboard-focusable scroll containers Opt Out

Thanks Di - this is a useful clarification. You can request up to 6 milestones for a Deprecation Trial, and only need a single LGTM. Renewals are possible, with sufficient justification. That said, if you do think that 9 milestones is sufficient for your needs - that is also possible, but

Re: [blink-dev] Re: Intent to Ship: Importmap integrity

I'm inclined to LGTM this now - but don't see a lot of harm waiting for 1 additional week (per Mozilla's request in the not-public minutes). Happy to do so before, so long as the HTML PR lands. On 5/22/24 5:15 AM, Yoav Weiss (@Shopify) wrote: On Wed, May 22, 2024 at 10:29 AM Yoav Weiss

Re: [blink-dev] Intent to Ship: Unrestricted WebUSB (available only to Isolated Web Apps)

Could you please request the various Privacy, Security, Enterprise, etc. review gates in your chromestatus entry? On 5/22/24 1:08 PM, 'Ajay Rahatekar' via blink-dev wrote: Contact emails mattreyno...@chromium.org Specification

Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

Yes, agree. Can we please request a position from Mozilla at https://github.com/mozilla/standards-positions/issues/new? On 5/22/24 6:43 PM, 'Daniel Clark' via blink-dev wrote: Yeah, that’s what I was trying to get at – the Intent implies that Gecko has also shipped the breaking change but it

Re: [blink-dev] RE: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

LGTM1 On Tue, May 21, 2024 at 3:07 PM 'Erik Anderson' via blink-dev < blink-dev@chromium.org> wrote: > Hi, > > > > Thanks for reaching out. > > > > We’ve reviewed the proposal and don’t have any significant concerns. We’ll > continue providing feedback via GitHub where appropriate. > > > >

RE: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

Yeah, that’s what I was trying to get at – the Intent implies that Gecko has also shipped the breaking change but it seems that might not be the case. If not, we should send a Request for Position to figure out whether there would be cross-browser alignment on shipping this. -- Dan From: Olli

[blink-dev] PSA - Privacy Sandbox APIs temporarily unavailable; fix deployed

On May 22nd at approximately 0:00 UTC, a misconfiguration in the Chrome-facilitated testing setup impacted the availability of the relevance and measurement APIs in all Chrome Stable versions. This

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

OK, thanks for outlining the spec mechanics :) Regardless of whether the PR actually lands in the spec, for the purpose of risk-assessment, it's even more interesting to know if the PR is *ready* to land in the spec. Can y'all clarify its review status? If it's ready to land, can a spec editor

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

Hi Dominik, Thanks for your add-up! And Yes, we can align with other browsers for the time being. -- ChangSeok > On May 21, 2024, at 6:13 AM, Dominik Röttsches wrote: > > Big thanks ChangSeok for implementing this and pushing for this feature. > > I can say a few things about the open

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

Hi Philip, I noticed that font-size-adjust-012.html, font-size-adjust-013.html, and parts of font-size-adjust-computed.html (e.g., ch-width and ic-width) show minor deviations from expected results. The exact issue with the WPT Linux machine is unclear since these tests can be affected by

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

Hi Vladimir, I requested the reviews in the chromestatus. Thanks. -- ChangSeok > On May 16, 2024, at 8:01 AM, Vladimir Levin wrote: > > > > On Thu, May 16, 2024 at 10:02 AM ChangSeok Oh wrote: > Contact emails > changseok...@bytedance.com, changs...@chromium.org > > Explainer > None > >

Re: [blink-dev] Intent to Ship: Unrestricted WebUSB (available only to Isolated Web Apps)

LGTM as an IWA OWNER (3x LGTM from Blink API OWNERS are still required according to the IWA-specific API launch process ). This is a good example of IWA-specific behavior minimally extending an existing API and I think this

[blink-dev] Intent to Ship: Unrestricted WebUSB (available only to Isolated Web Apps)

Contact emails mattreyno...@chromium.org Specification https://wicg.github.io/webusb/#permissions-policy Summary Enables trusted applications to bypass security restrictions in the WebUSB API. The WebUSB specification defines a blocklist of vulnerable devices and a table of protected

Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

I think it is because of this rather surprising non-backwards compatible recent change. On Wednesday, May 22, 2024 at 7:28:45 PM UTC+3 Daniel Clark wrote: > The Gecko status is marked as Shipped/Shipping and the Interop/Compat > section mentions Firefox having shipped this, but Firefox is

RE: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

The Gecko status is marked as Shipped/Shipping and the Interop/Compat section mentions Firefox having shipped this, but Firefox is still failing the WPTs at https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html. Can you help me understand the discrepancy there?

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate old CSS custom state syntax

To be particular about the usage number, it's about a magnitude more than our informal limit. That doesn't mean it can't be shipped, but it means that we want to be fairly certain that >90% of the users are unaffected by the change. How should I interpret the results from your investigation?

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate old CSS custom state syntax

On Tue, May 21, 2024 at 2:20 PM Joey Arhar wrote: > > Do you know what the breakage looks like > > I pushed to make sure that using the old syntax with CustomStateSet.add() > wouldn't throw exceptions when in the new mode in order to reduce breakage. > When websites use the old syntax after it's

Re: [blink-dev] Intent to Extend Deprecation Trial: Partitioning Storage, Service Workers, and Communication APIs

LGTM to extend the deprecation trial M127-M132 inclusive On Wed, May 22, 2024 at 4:44 PM Mike Taylor wrote: > On 5/22/24 8:11 AM, Yoav Weiss (@Shopify) wrote: > > > > On Tue, May 21, 2024 at 8:55 PM Mike Taylor > wrote: > >> *Contact emails* >> >> >> >> >> >> >> >> * miketa...@chromium.org

Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

LGTM to experiment with the new milestones (126 to 137) On Fri, May 17, 2024 at 4:52 PM mark a. foltz wrote: > On Wed, May 15, 2024 at 9:02 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Can you expand on how (if) this is different from the past intent >>

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

Please also fill out the Testing section on chromestatus.com. On Wed, May 22, 2024 at 7:50 AM 'Aaron Selya' via blink-dev < blink-dev@chromium.org> wrote: > Had a good initial conversation with them on Monday letting them know > about the issue. They're going to do some testing with the feature

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

LGTM3 On Wed, May 22, 2024 at 7:41 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM2 > > On Tuesday, May 21, 2024 at 2:11:37 PM UTC+2 Mike Taylor wrote: > >> Thanks Liam! >> >> LGTM1 to ship. >> On 5/20/24 3:51 PM, Liam Brady wrote: >> >> Thanks for your feedback on this intent!

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

Had a good initial conversation with them on Monday letting them know about the issue. They're going to do some testing with the feature enabled to try and gauge the impact the feature will have on their backend. I'm hopeful that they'll give us an update by early next week. On Wed, May 22, 2024

Re: [blink-dev] Intent to Extend Deprecation Trial: Partitioning Storage, Service Workers, and Communication APIs

On 5/22/24 8:11 AM, Yoav Weiss (@Shopify) wrote: On Tue, May 21, 2024 at 8:55 PM Mike Taylor wrote: ** *Contact emails* * miketa...@chromium.org Explainer https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md

Re: [blink-dev] Intent to Implement and Experiment: Skip Ad in Picture-in-Picture window

I went ahead and marked the review as started on chromestatus.com. On Wed, May 22, 2024 at 7:36 AM Daniel Bratell wrote: > Unfortunately it doesn't show up in the API Owner UI/ToDo list and I can't > directly see how to make it appear. jrobbins, is there anything strange > with this one? It is

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

LGTM2 On Tuesday, May 21, 2024 at 2:11:37 PM UTC+2 Mike Taylor wrote: > Thanks Liam! > > LGTM1 to ship. > On 5/20/24 3:51 PM, Liam Brady wrote: > > Thanks for your feedback on this intent! We plan on modifying the > "Allow-Cross-Origin-Event-Reporting" response header to accept a boolean >

Re: [blink-dev] Intent to Implement and Experiment: Skip Ad in Picture-in-Picture window

Unfortunately it doesn't show up in the API Owner UI/ToDo list and I can't directly see how to make it appear. jrobbins, is there anything strange with this one? It is very old so it might be different from anything done the last couple of years. /Daniel On 2024-05-17 22:39, 'Jiaming Cheng'

[blink-dev] Re: Question about "component_deps_blink Assignment had no effect" build error on ios.

Thanks Colin for the help, that was indeed the issue. On Tue, May 21, 2024 at 4:25 PM Colin Blundell wrote: > I missed this in the CL review, sorry - you have a dependency on Blink in > the component but iOS doesn't use Blink in its default build configuration. > Try building the iOS files only

[blink-dev] Intent to Ship: Dispatch selectionchange event per element

Contact emailsshuangshuang.z...@intel.com ExplainerNone Specificationhttps://w3c.github.io/selection-api/#selectionchange-event Summary Dispatches selectionchange event per element when this element(input/textarea) provides a text selection or its selection changes. This is to match the

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

Any news from Paypal? On Friday, May 3, 2024 at 7:15:58 PM UTC+2 Aaron Selya wrote: > Thank you for suggesting a deeper dive into this Yoav as I might not have > discovered the significant impact that the "receive-cookie-deprication" > cookies were having on my metrics without your prompting.

[blink-dev] Re: Intent to Ship: Importmap integrity

Kudos, Yoav! Excited to see rapid progress on this: Webkit PR is merged \o/, hoping to see this in M127, and fingers crossed for fast follow with FF. As background context and motivation, this is an important building block for enabling PCIv4 compliance for ecomm sites. v4 requires that the

Re: [blink-dev] Re: Intent to Ship: Compute Pressure

Could someone elaborate on why this won't be implemented for Android? It seems like a very useful thing to have, especially considering that the biggest amount of users with low end hardware who would stand to benefit are on Android. "Support on Android (incl. Android WebView) has been

Re: [blink-dev] Intent to Extend Deprecation Trial: Partitioning Storage, Service Workers, and Communication APIs

On Tue, May 21, 2024 at 8:55 PM Mike Taylor wrote: > *Contact emails* > > > > > > > > * miketa...@chromium.org Explainer > https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md > >

Re: [blink-dev] Re: Intent to Ship: Compute Pressure

On Tue, May 21, 2024 at 9:39 AM Raphael Kubo da Costa wrote: > > Op 17-05-2024 om 16:59 schreef Philip Jägenstedt: > > What will be the behavior on Android, will the API appear to work but > > never invoke the observer callback? If so, would it make sense to > > disable the feature on Android

[blink-dev] Re: Intent to Ship: Importmap integrity

On Wed, May 22, 2024 at 10:29 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Tuesday, May 21, 2024 at 1:04:44 PM UTC+2 Yoav Weiss wrote: > > Contact emailsyoavwe...@chromium.org > > Explainerhttps://github.com/guybedford/import-maps-extensions#integrity > >

[blink-dev] Re: Intent to Ship: Importmap integrity

On Tuesday, May 21, 2024 at 1:04:44 PM UTC+2 Yoav Weiss wrote: Contact emailsyoavwe...@chromium.org Explainerhttps://github.com/guybedford/import-maps-extensions#integrity Specificationhttps://github.com/whatwg/html/pull/10269 The PR is ready to land, but we're holding off on that for 2