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

Thanks, Shuangshuang On Thursday, May 23, 2024 at 9:29:59 AM UTC+8 mike...@chromium.org<mailto:mike...@chromium.org> wrote: 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

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

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 Ship: Multi-argument alt text in CSS Generated Content

adimir Levin Sent: Monday, May 13, 2024 11:44 AM To: Daniel Clark Cc: blink-dev@chromium.org Subject: Re: [blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content On Mon, May 13, 2024 at 2:23 PM 'Daniel Clark' via blink-dev mailto:blink-dev@chromium.org>> wro

[blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content

Contact emails dan...@microsoft.com Explainer None Specification https://drafts.csswg.org/css-content-3/#valdef-content---string--counter--attr and https://drafts.csswg.org/css-content-3/#alt Summary The CSS content property allows developers to specify

RE: [blink-dev] Intent to Ship: Support Video Chapter in MediaMetadata

I was curious about WPT coverage for this and found https://wpt.fyi/results/mediasession/mediametadata.html Maybe that could be updated to check for the basics of the new attribute? -- Dan From: 'Jiaming Cheng' via blink-dev Sent: Tuesday, April 30, 2024 1:50 PM To: blink-dev@chromium.org Cc:

[blink-dev] Intent to Prototype: Multi-argument alt text in CSS Generated Content

Contact emails dan...@microsoft.com Explainer None Specification https://www.w3.org/TR/css-content-3/#valdef-content---string--counter Summary The CSS content property allows developers to specify alternative text for accessibility with the following syntax:

RE: [blink-dev] Intent to Ship: EditContext API

irst, at which point my app reacts when it wasn't supposed to as the key was meant for the IME. Also, this table doesn't seem to match Firefox for example, pressing 's' when in Japanese input mode pops up the IME and in firefox it produces event.key = 'Process', not event.key = 's' which at leas

RE: [blink-dev] Intent to Ship: EditContext API

it wasn't supposed to as the key was meant for the IME. Also, this table doesn't seem to match Firefox for example, pressing 's' when in Japanese input mode pops up the IME and in firefox it produces event.key = 'Process', not event.key = 's' which at least makes more sense since the input should be go

RE: [blink-dev] Intent to Ship: EditContext API

d be going to the IME, not the page. On Tue, Oct 31, 2023 at 2:52 AM 'Daniel Clark' via blink-dev mailto:blink-dev@chromium.org>> wrote: Contact emails dan...@microsoft.com<mailto:dan...@microsoft.com>, sni...@microsoft.com<mailto:sni...@microsoft.com>, shih...@microsoft.

[blink-dev] Intent to Ship: EditContext API

Contact emails dan...@microsoft.com, sni...@microsoft.com, shih...@microsoft.com Explainer https://github.com/w3c/edit-context/blob/gh-pages/explainer.md Specification https://w3c.github.io/edit-context

RE: [blink-dev] Intent to Experiment: EditContext API

experiment assuming WPT caveats are addressed. On editing event order, perhaps we can track this separately. Is there a crbug for it? On Tuesday, June 13, 2023 at 9:02:34 PM UTC-7 Yoav Weiss wrote: On Wed, Jun 14, 2023 at 12:03 AM 'Daniel Clark' via blink-dev mailto:blink-dev@chromium.org>> wro

RE: [blink-dev] Intent to Experiment: EditContext API

crbug for it? On Tuesday, June 13, 2023 at 9:02:34 PM UTC-7 Yoav Weiss wrote: On Wed, Jun 14, 2023 at 12:03 AM 'Daniel Clark' via blink-dev mailto:blink-dev@chromium.org>> wrote: > Although in the template this is phrased as a yes/no question, can you say > more about the WPT coverage an

RE: [blink-dev] Intent to Experiment: EditContext API

ng mailto:shih...@microsoft.com>> Subject: Re: [blink-dev] Intent to Experiment: EditContext API Do you all have a timeline in mind for experimentation? On 6/12/23 7:00 PM, 'Daniel Clark' via blink-dev wrote: Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com

RE: [blink-dev] Intent to Experiment: EditContext API

for experimentation? On 6/12/23 7:00 PM, 'Daniel Clark' via blink-dev wrote: Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com>, shih...@microsoft.com<mailto:shih...@microsoft.com>, bemat...@microsoft.com<mailto:bemat...@microsoft.com>, dan...@microsoft.com<mailto

[blink-dev] Intent to Experiment: EditContext API

Contact emails sni...@microsoft.com, shih...@microsoft.com, bemat...@microsoft.com, dan...@microsoft.com Explainer

RE: [blink-dev] Intent to Ship: Custom Highlight API

Thanks for following through with that fix and reland! Highlight API has shipped: https://chromium-review.googlesource.com/c/chromium/src/+/3718885 From: Delan Azabani Sent: Friday, July 15, 2022 1:16 AM To: blink-dev Cc: Delan Azabani ; jme...@google.com ; Daniel Bratell ;

RE: [blink-dev] Intent to Ship: Custom Highlight API

%7C0%7C637933950515742925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=jQM8QtQRPqgZls%2F9HsfJrCfZgyS27G6dNHZeFIDr2sc%3Dreserved=0 On 08/06/2022 19:42, 'Daniel Clark' via blink-dev wrote: > > Contact emails &g

RE: [blink-dev] Intent to Ship: Custom Highlight API

agreement already but it'd be nice to confirm it, as this might change behavior if a different decision is made. Other than that I've just some minor comments inline. On 08/06/2022 19:42, 'Daniel Clark' via blink-dev wrote: > Risks > > > Interoperability and Compatibility > > L

RE: [blink-dev] Intent to Ship: Custom Highlight API

've just some minor comments inline. On 08/06/2022 19:42, 'Daniel Clark' via blink-dev wrote: > Risks > > > Interoperability and Compatibility > > Low risk: This feature received positive support from Safari and Firefox > at TPAC 2019. Safari is implementing it, Firefox

[blink-dev] Intent to Ship: Custom Highlight API

Contact emails dan...@microsoft.com, sa...@microsoft.com, ffi...@microsoft.com, lusan...@microsoft.com, pc...@microsoft.com, Explainer

RE: [blink-dev] Intent to Ship: Custom Highlight API

nd-in-page highlights to be built (conceptually if not physically) on top of this primitive? Rick On Thu, Aug 12, 2021 at 6:36 PM 'Daniel Clark' via blink-dev mailto:blink-dev@chromium.org>> wrote: Oh, you're right, I hadn't realized they still have it off by default. So my mail should have