LGTM1.
While it's unfortunate that the path to interop here might take longer than
we've hoped, it's very clear from the abundant linked documentation that
the team has done everything possible to set this feature up for success,
and meet the high bar set by our process. The spec PR has receive
Do you know if this works as expected with screen readers? I imagine the
pop up style rendering works since that's currently a common experience,
but not sure what would happen in an in-page rendering on mobile?
Thanks,
Vlad
On Thursday, September 4, 2025 at 9:55:18 PM UTC-4 Kent Tamura wrote:
I'd love for web developers who have been paying close attention to scroll
behaviour to weigh in here. This has been a deep well of sadness in a
cross-browser sense, and they might have opinions as to the benefits and
costs we aren't able to easily see. Spec compliance can either be great or
po
Contact emails
shanxing@intel.com
Explainer
None
Specification
https://www.w3.org/TR/webgpu/#texture-formats-tier1
Summary
Extend GPU texture format support with capabilities like render attachment,
blending, multisampling, resolve and storage_binding.
Blink component
Blink>WebGPU
We
Contact emails
mas...@chromium.org, chrom...@keithcirkel.co.uk
Explainer
https://open-ui.org/components/interest-invokers.explainer
Specification
https://github.com/whatwg/html/pull/11006
https://drafts.csswg.org/css-ui-4/#interest
https://drafts.csswg.org/selectors/#interest-pseudos
Summar
On 9/18/25 5:54 a.m., Philip Jägenstedt wrote:
Some additional context. Upgrading ICU can break sites and it cannot
be done with a flag because of the size of the library (two copies
would be needed). To mitigate the risk, we'd like to use the Blink
launch process going forward. Where we can i
Some additional context. Upgrading ICU can break sites and it cannot be
done with a flag because of the size of the library (two copies would be
needed). To mitigate the risk, we'd like to use the Blink launch process
going forward. Where we can identify a risk ahead of time, we can add a
targeted
Contact emails
hc...@chromium.org
Explainer
https://github.com/WICG/local-network-access/blob/main/explainer.md#websockets
Specification
https://wicg.github.io/local-network-access/#integration-with-websockets
Summary
Restricts the ability to make requests to the user's local network using
W
I completely agree, the point here isn't to follow the spec. The reason I
think we should follow the spec in this case is that it is more ergonomic
and predictable when applying overscroll-behavior doesn't just work
sometimes. I think that developers are rightfully confused by those cases
where it
Hi Carlos - that's correct. We've ended the experiments removing the HTTP
header as we were unable to provide a sufficient alternative, resulting in
breakage to important abuse and fraud prevention use cases.
Thanks,
Peter
On Sat, Sep 6, 2025 at 5:32 PM Carlos Solorzano
wrote:
> Sorry if this i
Contact emails
hc...@chromium.org
Explainer
https://github.com/WICG/local-network-access/blob/main/explainer.md
Specification
https://wicg.github.io/local-network-access/#integration-with-webtransport
Summary
Restricts the ability to make requests to the user's local network using
WebTranspo
On Thu, Sep 18, 2025 at 2:51 PM Mike Taylor wrote:
> On 9/18/25 5:54 a.m., Philip Jägenstedt wrote:
>
> Some additional context. Upgrading ICU can break sites and it cannot be
> done with a flag because of the size of the library (two copies would be
> needed). To mitigate the risk, we'd like to
Contact emails
lwar...@igalia.com
Explainer
https://github.com/Igalia/explainers/tree/main/nodes-from-rect
Specification
None
Summary
An API on Document for returning the sequence of elements or text nodes within
a rectangle.
Blink component
Blink>Editing>Selection
Web Feature ID
Missing
*Contact emails*
pmee...@chromium.org
*Explainer*
https://docs.google.com/document/d/1uAutnUWpC6V-ka_MA-4m74YV12LAA6qP1sYjy97S2-0/edit?usp=sharing
*Specification*
https://github.com/httpwg/http-extensions/issues/2649
*Design docs*
https://docs.google.com/document/d/1uAutnUWpC6V-ka_MA-4m74YV12LA
Oops, the CLDR version is 47, not 46. I'll update the chromestatus entry.
On Thu, Sep 18, 2025 at 11:40 AM Chromestatus <
ad...@cr-status.appspotmail.com> wrote:
> *Contact emails*
> foo...@chromium.org, ko...@chromium.org
>
> *Explainer*
> None
>
> *Specification*
> https://tc39.es/ecma402
>
> *
Hi Yoav,
Yes, this is controlled by developers.
Currently, when fetching the client metadata endpoint, the browser sends
the API caller's origin and client ID to the IdP. With this proposal, if
the API is called from within a cross-site iframe (and allowed by the
embedder via a permissions policy
Contact emails
nrosent...@chromium.org, vmp...@chromium.org
Explainer
https://github.com/w3c/csswg-drafts/blob/main/css-view-transitions-2/two-phase-transition-explainer.md
Specification
None
Summary
Currently, cross-document view transitions are only captured when the new
document's respons
Contact emails
foo...@chromium.org, ko...@chromium.org
Explainer
None
Specification
https://tc39.es/ecma402
Design docs
https://unicode-org.github.io/icu/download/77.html
https://cldr.unicode.org/downloads/cldr-46
https://www.unicode.org/versions/Unicode16.0.0
Summary
ICU is not a feature
18 matches
Mail list logo
