blink-dev

Contact emails jlav...@google.com, andres...@chromium.org, fma...@chromium.org, schenney@

Thanks - LGTM to experiment from 143 to 148 inclusive. On 11/4/25 1:37 pm, 'Lia Hiscock' via

If you do not ship a Payment Handler or integrate Payment Request into your website, you can stop

LGTM1 On 10/28/25 10:05 am, Minseong Kim wrote: Contact emails jja0...@gmail.com Specification https

On 10/29/25 7:34 am, Chromestatus wrote: Contact emails sche...@chromium.org, zs...@igalia.com

LGTM2 On 10/29/25 10:57 am, Daniel Bratell wrote: LGTM1 /Daniel On 2025-10-29 15:44, Chromestatus

Reading the issue, it looks like they've figured out the issue, which involves iframes and

Hello, Could you please request reviews for the Privacy, Security, Enterprise, Debuggability, and

The previous launch had a kill switch: `kDontDecodeAsciiPercentEncodedURLPath` (see https://crrev.com

Gecko: No signal WebKit: No signal Could you file for standards positions as well? Seems this was not

Well technically XPath is an autonous language and is a strong basis of XSLT (1) It would help to

Contact emails ft...@google.com Specification https://tc39.es/ecma402/#sec-Intl.Locale.prototype.

Contact emails dr...@chromium.org Explainer No information provided Specification https://www.w3.org/

blink-dev isn't really the right place to raise this issue, but I will try to pass this along to

Contact emails jlav...@google.com, andres...@chromium.org, fma...@chromium.org, schenney@

Reaching out to site owners was mostly for a sanity check that the resource is not expecting to be

Contact emails m...@chromium.org Explainer https://github.com/WICG/manifest-incubations/blob/gh-pages/

Thank you Deepti - ample evidence of progress here as well. LGTM to extend 3 more milestones (M143 to

Thank you Deepti - ample evidence of progress here. LGTM to extend 3 more milestones (M143 to M145

Hi! Within the scope of this launch the API was exposed just to `Window`, despite the spec mentioning

On Wed, Oct 29, 2025 at 5:51 PM Joey Arhar <jar...@chromium.org> wrote: > is this approach

LGTM3 On Tue, Oct 28, 2025 at 1:19 PM Daniel Bratell <brat...@gmail.com> wrote: LGTM2 /Daniel

I'm not sure how that would work for primitive types without an optional type or requiring a

Contact emails jka...@chromium.org, k...@google.com, lin...@chromium.org Documentation https://

Thanks Rohan. It looks to me like the discussion has converged on the core aspects of the design. So

LGTM3 On Wednesday, October 29, 2025 at 11:10:37 AM UTC-4 Alex Russell wrote: LGTM2 On Wednesday,

LGTM3 On Tuesday, October 28, 2025 at 2:26:12 PM UTC+1 Mike Taylor wrote: LGTM2 On 10/22/25 7:35 pm,

LGTM3 On Saturday, October 25, 2025 at 4:56:13 PM UTC+2 Mike Taylor wrote: I see, thanks. Marking

LGTM3 to ship and deprecate (but not yet remove). On Fri, Oct 24, 2025 at 8:36 AM Mike Taylor <

Just to be clear: anchored elements *will* respond to transform changes on the anchor, and be re-laid