Re: [blink-dev] Intent to Ship: Back/forward cache NotRestoredReasons API

I am happy with the spec progress here and don't think it's a significant blocker for the Intent at this point. On the tests and implementation: - I found performance-navigation-timing-navigation-failure.tentative.window.js

Re: [blink-dev] Intent to Ship: field-sizing CSS property

The HTML PR is merged; thanks Philip, and Simon from Mozilla, for their reviews. LGTM2! On Thu, Dec 21, 2023 at 9:08 AM TAMURA, Kent wrote: > I'm not sure how long it will take until the HTML PR is merged. > Involving a WebKit people sounds helpful. I'll try it. > > On Thu, Dec 21, 2023 at 1:5

Re: [blink-dev] Intent to Ship: Cross App and Web Attribution Measurement

Hi Nan, On 2/2/24 5:00 AM, Nan Lin wrote: Contact emails lin...@chromium.org , johni...@chromium.org Explainer Cross App and Web Attribution Measurement

[blink-dev] Code Search Indexer changing, should be transparent to users

Hi folks, The Code Search team is launching a new multi-branch indexing pipeline for Chromium Code Search at source.chromium.org. This is rolling out gradually over the next few weeks starting today, and the change should be completely transparent to users. This change in indexer will let Code Se

Re: [blink-dev] Intent to Prototype and Ship: Standardized CSS zoom

The link to the specification: https://github.com/w3c/csswg-drafts/pull/9699 list behaviors and then says > Web compat analysis: the above is what is already implemented in WebKit and Chromium browsers But one of the behaviors listed is > devicePixelRatio is affected by zoom inherited from a

Re: [blink-dev] Re: Intent to Ship: New ALPS code point

LGTM2 On Mon, Feb 5, 2024 at 5:38 PM Yoav Weiss (@Shopify) wrote: > LGTM1 > > Thanks for including these values in the I-D. > > On Fri, Feb 2, 2024 at 9:17 PM Victor Tan wrote: > >> the code point PR is merged. Feel free to take a look again. Thanks. >> >> On Wednesday, January 24, 2024 at 3:34

[blink-dev] Changes to release workflows in the new Chromium Issue Tracker

Hi all, Chromium has moved to its new issue tracker, and critical release information has been migrated from labels to custom fields . Release workflows have been updated to support these new fields: - How to request a merge: add the applicable milestone(s) to the issue’s Merge-Request

Re: [blink-dev] Re: Intent to Ship: New ALPS code point

LGTM1 Thanks for including these values in the I-D. On Fri, Feb 2, 2024 at 9:17 PM Victor Tan wrote: > the code point PR is merged. Feel free to take a look again. Thanks. > > On Wednesday, January 24, 2024 at 3:34:44 PM UTC-5 Victor Tan wrote: > >> create a PR for the code point change on the

Re: [blink-dev] Intent to Ship: Back/forward cache NotRestoredReasons API

This is now ready to ship, now that we have all the approvals on the ChromeStatus and the spec draft is close to agreement. Can you please take a look at this again? Thanks! On