Groups
Sign in
Groups
blink-dev
Conversations
About
Send feedback
Help
Sort By Relevance
Sort By Date
1–30 of many
Mason Freed
, …
Mason Freed
13
12:04 PM
Intent to Ship: Deprecation of non-standard declarative shadow DOM serialization
as I
ship
this. Thanks, Mason On Fri, Jul 26, 2024 at 8:48 AM Chris Harrelson wrote: > LGTM3 > > On Fri, Jul 26, 2024, 8:42 AM Rick Byers wrote: > >> I'm a bit worried
unread,
Intent to Ship: Deprecation of non-standard declarative shadow DOM serialization
as I
ship
this. Thanks, Mason On Fri, Jul 26, 2024 at 8:48 AM Chris Harrelson wrote: > LGTM3 > > On Fri, Jul 26, 2024, 8:42 AM Rick Byers wrote: > >> I'm a bit worried
12:04 PM
Mason Freed
, …
Mike Taylor
8
11:58 AM
Intent to Ship: Rename position-try-options to position-try-fallbacks
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
unread,
Intent to Ship: Rename position-try-options to position-try-fallbacks
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
11:58 AM
Akash Nadan
, …
Yoav Weiss (@Shopify)
8
10:50 AM
Intent to Ship: Attribution Reporting Feature: Changes to source-destination-limit logic
Does this
intent
deprecate or change behavior of existing APIs, such >>>>>> that it has potentially high risk for Android WebView-based applications? >>
unread,
Intent to Ship: Attribution Reporting Feature: Changes to source-destination-limit logic
Does this
intent
deprecate or change behavior of existing APIs, such >>>>>> that it has potentially high risk for Android WebView-based applications? >>
10:50 AM
Martin Kreichgauer
, …
Yoav Weiss (@Shopify)
9
7:30 AM
Intent to Ship: Web Authentication API: JSON serialization methods
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
unread,
Intent to Ship: Web Authentication API: JSON serialization methods
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
7:30 AM
Paul Jensen
, …
Yoav Weiss (@Shopify)
3
5:28 AM
Intent to Ship: Protected Audience: cross-origin trusted signals fetches
> This
intent
message was generated by Chrome Platform Status >> . >> >> -- >> You received this message because you are subscribed to the Google Groups
unread,
Intent to Ship: Protected Audience: cross-origin trusted signals fetches
> This
intent
message was generated by Chrome Platform Status >> . >> >> -- >> You received this message because you are subscribed to the Google Groups
5:28 AM
Yoav Weiss (@Shopify)
,
Shuangshuang Zhou
2
5:24 AM
Re: [blink-dev] Intent to Ship:
Does this
intent
deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> Low WebView
unread,
Re: [blink-dev] Intent to Ship:
Does this
intent
deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> Low WebView
5:24 AM
Alex Turner
, …
Yoav Weiss (@Shopify)
7
5:03 AM
Intent to Ship: Private Aggregation API: filtering IDs
LGTM2 On Friday, July 19, 2024 at 6:56:59 PM UTC+2 Mike Taylor wrote: > LGTM1 > On 7/17/24 5:24 PM, Alex Turner wrote: > > On Mon, Jul 15,
unread,
Intent to Ship: Private Aggregation API: filtering IDs
LGTM2 On Friday, July 19, 2024 at 6:56:59 PM UTC+2 Mike Taylor wrote: > LGTM1 > On 7/17/24 5:24 PM, Alex Turner wrote: > > On Mon, Jul 15,
5:03 AM
Akash Nadan
, …
Yoav Weiss (@Shopify)
5
5:02 AM
Intent to Ship: Attribution Reporting Feature: Flexible contributions filtering
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
unread,
Intent to Ship: Attribution Reporting Feature: Flexible contributions filtering
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
5:02 AM
David Baron
, …
Domenic Denicola
8
Jul 25
Intent to Ship: CSS interpolate-size property and calc-size() function
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
unread,
Intent to Ship: CSS interpolate-size property and calc-size() function
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
Jul 25
Robbie McElrath
, …
Daniel Bratell
7
Jul 24
Intent to Ship: Isolated Web Apps
to previous
Intent
discussions > >
Intent
to prototype: https://groups.google.com/a/ch > romium.org/d/msgid/blink-dev/CAEmk%3DMayyUjocrvyQKgu-bZy_ > 4z5VJ0ijHCAijBTZY2xLwJpJQ
unread,
Intent to Ship: Isolated Web Apps
to previous
Intent
discussions > >
Intent
to prototype: https://groups.google.com/a/ch > romium.org/d/msgid/blink-dev/CAEmk%3DMayyUjocrvyQKgu-bZy_ > 4z5VJ0ijHCAijBTZY2xLwJpJQ
Jul 24
Peter Birk Pakkenberg
, …
Daniel Bratell
7
Jul 24
Intent to Ship: Web Permissions API on WebView
> This
Intent
to
Ship
covers the launch of the Web >>> Permission API in WebView, an API that has already >>> launched in other browsers and embedders. >>
unread,
Intent to Ship: Web Permissions API on WebView
> This
Intent
to
Ship
covers the launch of the Web >>> Permission API in WebView, an API that has already >>> launched in other browsers and embedders. >>
Jul 24
Shuangshuang Zhou
, …
Domenic Denicola
5
Jul 24
Intent to Ship: Coalesce selectionchange events
Does this
intent
deprecate or change behavior of existing APIs, such >>>> that it has potentially high risk for Android WebView-based applications? >>>>
unread,
Intent to Ship: Coalesce selectionchange events
Does this
intent
deprecate or change behavior of existing APIs, such >>>> that it has potentially high risk for Android WebView-based applications? >>>>
Jul 24
Simon Hangl
, …
Swetha Sivaram
20
Jul 24
Intent to Extend Experiment: Capture all screens
API to
ship
>>>> >>>> . >>>> - This is partially on us, the API owners. Artur's comment on >>>> that thread should have triggered
unread,
Intent to Extend Experiment: Capture all screens
API to
ship
>>>> >>>> . >>>> - This is partially on us, the API owners. Artur's comment on >>>> that thread should have triggered
Jul 24
Mustaq Ahmed
, …
Mike Taylor
7
Jul 22
Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts
Does this
intent
deprecate or change behavior of >> existing APIs, such that it has potentially high risk >> for Android WebView-based applications? >> >>
unread,
Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts
Does this
intent
deprecate or change behavior of >> existing APIs, such that it has potentially high risk >> for Android WebView-based applications? >> >>
Jul 22
Dylan Cutler
, …
Ben Wiser
14
Jul 22
Intent to Deprecate and Relaunch: CHIPS on WebView
plan to
ship
the changes here is, but it >>>>> may take some time due to the changes being more involved and a bigger >>>>> compat risk than initially
unread,
Intent to Deprecate and Relaunch: CHIPS on WebView
plan to
ship
the changes here is, but it >>>>> may take some time due to the changes being more involved and a bigger >>>>> compat risk than initially
Jul 22
Christopher Cameron
, …
Larry LACa
9
Jul 19
Intent to Ship: WebGPU extended range (HDR) support
ready to
ship
. It has been split off and reduced in scope from this >>> wider feature . >>> Contact emailsccam...@chromium.org >>> >>> ExplainerNone
unread,
Intent to Ship: WebGPU extended range (HDR) support
ready to
ship
. It has been split off and reduced in scope from this >>> wider feature . >>> Contact emailsccam...@chromium.org >>> >>> ExplainerNone
Jul 19
Reilly Grant
, …
Andrey Safonov
31
Jul 18
Intent to Implement and Ship: WebUSB Interface Class Filtering
Yes, I agree with Luke. It seems that this decision was made hastily and inflexibly, making it challenging to develop applications that require deeper
unread,
Intent to Implement and Ship: WebUSB Interface Class Filtering
Yes, I agree with Luke. It seems that this decision was made hastily and inflexibly, making it challenging to develop applications that require deeper
Jul 18
Ajay Rahatekar
, …
Daniel Bratell
6
Jul 17
Intent to Ship: AudioContext.onerror
Does this
intent
deprecate or change behavior of existing >> APIs, such that it has potentially high risk for Android >> WebView-based applications? >> >>
unread,
Intent to Ship: AudioContext.onerror
Does this
intent
deprecate or change behavior of existing >> APIs, such that it has potentially high risk for Android >> WebView-based applications? >> >>
Jul 17
Yaroslav Shalivskyy
, …
William Smith
18
Jul 16
Intent to Ship: Used color scheme root scrollbars
. The
intent
should request, privacy, security, >>>>>>>>>>>> enterprise, and the other steps there. >>>>>>>>
unread,
Intent to Ship: Used color scheme root scrollbars
. The
intent
should request, privacy, security, >>>>>>>>>>>> enterprise, and the other steps there. >>>>>>>>
Jul 16
Martin Kreichgauer
,
Mike Taylor
3
Jul 12
Ready for Developer Testing: Web Authentication API: JSON serialization methods
be an
Intent
to
Ship
, or dev trial? > > thanks, > Mike > On 6/26/24 2:28 PM, 'Martin Kreichgauer' via blink-dev wrote: > > Contact emails martinkr@google
unread,
Ready for Developer Testing: Web Authentication API: JSON serialization methods
be an
Intent
to
Ship
, or dev trial? > > thanks, > Mike > On 6/26/24 2:28 PM, 'Martin Kreichgauer' via blink-dev wrote: > > Contact emails martinkr@google
Jul 12
Mason Freed
, …
Mike Taylor
7
Jul 11
Intent to Ship: Rename inset-area to position-area
: this
intent
is to add `position-area` which is a drop >>>> in replacement/alias for `inset-area`. The latter is being deprecated via >>>> another
intent
unread,
Intent to Ship: Rename inset-area to position-area
: this
intent
is to add `position-area` which is a drop >>>> in replacement/alias for `inset-area`. The latter is being deprecated via >>>> another
intent
Jul 11
Mike Taylor
, …
Brett McStotts
82
Jul 11
Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs
hasStorageAccess/hasUnpartitionedCookieAccess doesn't tell us if storage partitioning is disabled. It just tells you if there is unpartitioned
unread,
Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs
hasStorageAccess/hasUnpartitionedCookieAccess doesn't tell us if storage partitioning is disabled. It just tells you if there is unpartitioned
Jul 11
Emanuel Ziegler
, …
Yoav Weiss (@Shopify)
7
Jul 11
Intent to Extend Experiment: WebAssembly JS String Builtins
from your
intent
, but I should have asked for clarifications on that front. Apologies! > > Also, there was significant progress on the spec since the last extension. > The
unread,
Intent to Extend Experiment: WebAssembly JS String Builtins
from your
intent
, but I should have asked for clarifications on that front. Apologies! > > Also, there was significant progress on the spec since the last extension. > The
Jul 11
Mason Freed
,
Yoav Weiss (@Shopify)
4
Jul 10
Web-Facing Change PSA: Rename inset-area to position-area
these >
intent
emails. I was assuming this still requires 3 LGTMs from owners. > I've obsoleted this chromestatus entry, and created a fresh one with the correct (I think
unread,
Web-Facing Change PSA: Rename inset-area to position-area
these >
intent
emails. I was assuming this still requires 3 LGTMs from owners. > I've obsoleted this chromestatus entry, and created a fresh one with the correct (I think
Jul 10
Amos Lim
, …
Chris Harrelson
9
Jul 10
Intent to Ship: CSSImportRule.styleSheet
discussed this
intent
in the API Owner meeting, and I ended up with > some questions. > > Question 1: What is the current behaviour in the case where the > specification wants
unread,
Intent to Ship: CSSImportRule.styleSheet
discussed this
intent
in the API Owner meeting, and I ended up with > some questions. > > Question 1: What is the current behaviour in the case where the > specification wants
Jul 10
Yi Gu
, …
Yoav Weiss (@Shopify)
9
Jul 9
Intent to Experiment: FedCM Button Mode API and Use Other Account API
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
unread,
Intent to Experiment: FedCM Button Mode API and Use Other Account API
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
Jul 9
Shu-yu Guo
, …
Yoav Weiss (@Shopify)
6
Jul 8
Intent to Ship: Promise.try
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
unread,
Intent to Ship: Promise.try
Does this
intent
deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>
Jul 8
Frank Tang
,
Daniel Bratell
2
Jul 3
Ready for Developer Testing: Intl.DurationFormat
be an
Intent
to
Ship
, right? It isn't in that state in ChromeStatus so it doesn't appear on the todo lists right now. Maybe you can navigate it to the right state and get the prerequisite
unread,
Ready for Developer Testing: Intl.DurationFormat
be an
Intent
to
Ship
, right? It isn't in that state in ChromeStatus so it doesn't appear on the todo lists right now. Maybe you can navigate it to the right state and get the prerequisite
Jul 3
Sahir Vellani
, …
Sahir Vellani
46
Jul 3
Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking
Thank you everyone. Appreciate all your help for each step of the process!! On Wednesday, July 3, 2024 at 8:50:20 AM UTC-7 mike...@chromium.org wrote:
unread,
Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking
Thank you everyone. Appreciate all your help for each step of the process!! On Wednesday, July 3, 2024 at 8:50:20 AM UTC-7 mike...@chromium.org wrote:
Jul 3
Anders Hartvoll Ruud
, …
Chris Harrelson
6
Jul 3
Intent to Ship: CSS Anchor Positioning: Unwrapped inset-area()
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
unread,
Intent to Ship: CSS Anchor Positioning: Unwrapped inset-area()
Does this
intent
deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>
Jul 3