[blink-dev] Intent to Ship: CSS scroll-target-group property

Contact emailssakha...@chromium.org ExplainerCurrently to create carousel or table of contents patterns authors can use ::scroll-marker pseudo elements to create navigation elements. As they are pseudo elements they have a number of limitations. The scroll-target-group property allows to overcome

[blink-dev] Intent to Ship: CSS typed arithmetic

Contact emails sakha...@chromium.org Explainer None Specification https://www.w3.org/TR/css-values-4/#calc-type-checking Summary Typed arithmetic allows to write expressions in CSS such a calc(10em / 1px) or calc(20% / 0.5em * 1px) which is useful for eg typography, as it allows to convert

[blink-dev] Intent to Ship: CSS counter() and counters() in alt text of 'content' property

Contact emailssakha...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-content/#content-property Summary counter() and counters() in alt text of 'content' property is useful to provide more meaningful information to e.g. pseudo elements to improve their accessibility. Bli

Re: [blink-dev] Intent to Experiment: Script Blocking in Incognito

Hey Yoav, thanks for your questions! On Monday, June 16, 2025 at 5:11:02 PM UTC+2 Yoav Weiss wrote: On Mon, Jun 16, 2025 at 4:24 PM 'Zainab Rizvi' via blink-dev < blink-dev@chromium.org> wrote: Contact emailsriz...@google.com, mk...@chromium.org Explainerhttps://github.com/explainers-by-googler

Re: [blink-dev] Intent to Experiment: Script Blocking in Incognito

On Mon, Jun 16, 2025 at 4:24 PM 'Zainab Rizvi' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsriz...@google.com, mk...@chromium.org > > Explainerhttps://github.com/explainers-by-googlers/script-blocking > > Specification > https://github.com/explainers-by-googlers/script-blocking/b

[blink-dev] Intent to Experiment: Script Blocking in Incognito

Contact emailsriz...@google.com, mk...@chromium.org Explainerhttps://github.com/explainers-by-googlers/script-blocking Specification https://github.com/explainers-by-googlers/script-blocking/blob/main/index.bs Summary Mitigating API Misuse for Browser Re-Identification, otherwise known as Scrip

Re: [blink-dev] Re: Intent to Ship: Allow more characters in javascript DOM APIs

LGTM2 /Daniel On 2025-06-13 03:42, TAMURA, Kent wrote: LGTM1. The risk by shipping this feature would be very small. On Fri, Jun 13, 2025 at 10:39 AM Domenic Denicola wrote: I'll recuse myself from LGTMing this given that I drove the spec work, but I want to encourage other API ow

[blink-dev] Re: Intent to Ship: Insert CJK inter-script spacing: the CSS `text-autospace` property

Thanks for these updates. Do you have any ideas on when the WebKit difference might be resolved? We shouldn't block shipping on them, but if there's a chance that the initial value might change due to ongoing discussions, it would be good to know that before we ship. On Fri, Jun 13, 2025 at 3:43 P

Re: [blink-dev] Re: Intent to Ship: CSS Corner shaping (corner-shape, superellipse, squircle)

Excited to see this! Has the TAG weighed in on the proliferation of related but different shorthand syntaxes in this area? We have `superellipse()` here and `cubic-bezier()` in easing. Should we provide both in each system? If not, why not? Best, Alex On Mon, Jun 16, 2025, 5:27 AM Domenic Denic

[blink-dev] Web-Facing Change PSA: Scroll Anchoring Priority Candidate Fix

Contact emailsvmp...@chromium.org SpecificationNone Summary Currently, scroll anchoring algorithm selects priority candidates when they are available as anchor targets. The priority candidates are currently a focused editable element and find-in-page highlights. This can cause suboptimal user ex

[blink-dev] Intent to [Experiment] Origin Trial: Incoming Call Notifications

Spec The shape of the API and discussions are based on this explainer. Intended to live in the Notifications API spec. Summary We would like

Re: [blink-dev] Re: Intent to Ship: CSS Corner shaping (corner-shape, superellipse, squircle)

On Mon, Jun 16, 2025 at 9:22 PM Alex Russell wrote: > Excited to see this! > > Has the TAG weighed in on the proliferation of related but different > shorthand syntaxes in this area? We have `superellipse()` here and > `cubic-bezier()` in easing. Should we provide both in each system? If not, > w