Re: [blink-dev] Intent to Ship: Coalesce selectionchange events

On Tue, Jul 23, 2024 at 3:08 AM Shuangshuang Zhou < shuangshuang.z...@intel.com> wrote: > Contact emailsshuangshuang.z...@intel.com > > ExplainerNone > > Specification > https://w3c.github.io/selection-api/#scheduling-selectionhange-event > > Summary > > This feature is not to fire

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

should have resulted in the original OT never landing. That would have >>> avoided the mess we're in now. >>>- Multiple milestones where the OT ran without any public approval >>>from the API owners. >>> >>> Beyond that, it's

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

eted. LGTM1 > Also, could you start the various reviews on the chromestatus entry? > > Done! > > Dylan > > On Wed, Jul 17, 2024 at 2:03 PM Vladimir Levin > wrote: > >> Thank you for all of the context. >> >> I agree that deleting the affected cooki

Re: [blink-dev] Intent to Ship: WebGPU extended range (HDR) support

LGTM2 On Wed, Jul 17, 2024 at 10:09 PM Domenic Denicola wrote: > > > On Wednesday, July 17, 2024 at 10:41:26 AM UTC+9 Domenic Denicola wrote: > > This looks like a nice straightforward feature. Just one potential spec > issue... > > On Tue, Jul 16, 2024 at 11:19 PM 'Christopher Cameron' via

Re: [blink-dev] Intent to Ship: Rename position-try-options to position-try-fallbacks

On Wed, Jul 10, 2024 at 6:34 PM Mason Freed wrote: > {NOTE: this is a replacement of this chromestatus > , which has the wrong > feature type and cannot be changed.} > Contact emailsmas...@chromium.org, andr...@chromium.org > > ExplainerNone > >

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

including M131. If more time is needed, you can come back for another extension with evidence of substantial progress (e.g. shipping the feature on top of IWA). Thanks, Vlad > > On Wednesday, July 17, 2024 at 6:45:44 PM UTC+2 Daniel Bratell wrote: > >> LGTM2 >> >> /Dan

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

On Thu, Jul 11, 2024 at 1:17 PM Torne (Richard Coles) wrote: > > > On Tue, 9 Jul 2024 at 10:20, Vladimir Levin wrote: > >> >> >> On Fri, Jun 28, 2024, 16:28 'Dylan Cutler' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Hey Vlad, >&g

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

esday, June 25, 2024 at 7:48:07 PM UTC+2 Daniel Bratell wrote: >>>>> >>>>>> Any reason to not make it available for everyone? Asking for a friend. >>>>>> >>>>>> Another thing, when extending experiments we want to see evidence of >&

Re: [blink-dev] Intent to Ship: Rename inset-area to position-area

LGTM1 to add `position-area`, since it is an alias for `inset-area` that is shipped and is being deprecated. On Thu, Jul 11, 2024 at 12:22 PM Mason Freed wrote: > > On Thu, Jul 11, 2024 at 9:17 AM Vladimir Levin > wrote: > >> Just to clarify: this intent is to add `po

Re: [blink-dev] Intent to Ship: Rename inset-area to position-area

Just to clarify: 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. Is this correct? Thanks, Vlad On Wed, Jul 10, 2024 at 6:23 PM Mason Freed wrote: > {NOTE: this is a replacement of this chromestatus

Re: [blink-dev] Intent to Deprecate and Remove: Deprecation of CSS Anchor Positioning property `inset-area`

On Thu, Jul 11, 2024 at 11:52 AM Mason Freed wrote: > > > On Thu, Jul 11, 2024 at 8:31 AM Vladimir Levin > wrote: > >> From the other emails, there is a 0.02% usage of this property right now, >> so it may be worthwhile to document the planned timelin

Re: [blink-dev] Intent to Deprecate and Remove: Deprecation of CSS Anchor Positioning property `inset-area`

On Wed, Jul 10, 2024 at 6:10 PM 'Ajay Rahatekar' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsmas...@chromium.org > > ExplainerNone > > Specification > https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001 > > Summary > > The CSSWG resolved to rename the

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

used in these cases? I'm trying to estimate actual inconsistent behavior that this is trying to fix and if that worth the risk of breakage for all partitioned cookies Also, what's the timeline for shipping the cookie manager fix that would be able to deal with partitioned cookies properly? Tha

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

On Tue, Jun 25, 2024 at 4:27 PM Stefan Zager wrote: > On Tue, Jun 25, 2024 at 8:26 AM Vladimir Levin > wrote: > >> >> >> On Mon, Jun 24, 2024 at 5:54 PM Stefan Zager wrote: >> >>> Hey all, >>> >>> I recently took over o

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

On Mon, Jun 24, 2024 at 5:54 PM Stefan Zager wrote: > Hey all, > > I recently took over ownership of this project, and I have a couple of > updates... > > - The target launch milestone is now M128. > > - In addition to the changes in functionality previously discussed, we are > going to ship a

Re: [blink-dev] Re: Intent to Prototype and Ship: Compute Pressure WebDriver endpoints

LGTM2 On Mon, Jun 24, 2024 at 3:05 PM Mike Taylor wrote: > Thanks - LGTM1 > > On 6/24/24 11:02 AM, Raphael Kubo da Costa wrote: > > Done! > > > > Mike Taylor writes: > >> Could you please request reviews for the various review gate bits in > >> your chromestatus entry? > >> > >> > >> (privacy,

Re: [blink-dev] Intent to Implement and Ship: aria-rowindextext and aria-colindextext

LGTM1, thanks On Wed, Jun 12, 2024 at 2:35 PM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > *Contact emails* > > dan...@microsoft.com > > > > *Explainer* > > No formal explainer but https://github.com/w3c/aria/issues/667 discusses > use cases and alternatives. > > > >

Re: [blink-dev] Intent to Ship: WebAuthn hints

Hi, Is it possible to put together a small explainer for this. It's a bit difficult to understand what this hint would control. Do you have examples? Thanks, Vlad On Wednesday, June 5, 2024 at 1:11:27 PM UTC-4 Adam Langley wrote: > On Tue, Jun 4, 2024 at 7:26 PM Mike Taylor wrote: > >>

Re: [blink-dev] Re: Intent to Ship: SkipAd media session action

LGTM2 On Tue, Jun 11, 2024 at 3:42 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > On Tue, Jun 11, 2024 at 12:14 AM 'Jiaming Cheng' via blink-dev < > blink-dev@chromium.org> wrote: > >> Thanks François for the info! >> >> Hi Philip, please let us know if you have any other

Re: [blink-dev] Intent to Ship: Protected Audience: Allow trusted bidding signals to trigger interest group updates

11, 2024 at 11:46:09 AM UTC-4 Vladimir Levin wrote: > >> I think this is an improvement to the platform. My only small (bikeshed) >> concern is the name of the variable: updateIfOlderThanMs. Instead of a day, >> it seems that we're going down to millisecond level. The spec a

Re: [blink-dev] Intent to Ship: Protected Audience: Allow trusted bidding signals to trigger interest group updates

I think this is an improvement to the platform. My only small (bikeshed) concern is the name of the variable: updateIfOlderThanMs. Instead of a day, it seems that we're going down to millisecond level. The spec also says > An `updateIfOlderThanMs` that's less than 10 minutes will be clamped to 10

Re: [blink-dev] Intent to Ship: Protected Audience - Fix implementation and spec for renderSize

Hi, Can you please start the various reviews in chromestatus? [image: chipsna.png] Thanks, Vlad On Fri, Jun 7, 2024 at 11:10 AM 'Xiaochen Zhou' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > xiaoche...@google.com, shivani...@google.com, jkar...@google.com > > Explainer > >

Re: [blink-dev] Intent to Ship: CSS ruby-align property

LGTM3 On Thu, Jun 6, 2024 at 9:28 PM Mike Taylor wrote: > LGTM2 > On 6/7/24 1:39 AM, Chris Harrelson wrote: > > Sorry, make that "LGTM1" > > On Thu, Jun 6, 2024 at 9:39 AM chrishtr via Chromestatus < > admin+chris...@cr-status.appspotmail.com> wrote: > >> LGTM >> -- >> You received this message

Re: [blink-dev] Intent to Ship: No-Vary-Search Hint for Prerender Speculation Rules

ult in the absence of the hint. > That makes sense. It seems like the expectation is that this hint would only be used in cases where developers are optimizing on hover to save as much time as possible, so it makes sense that racing or having wasted work is undesired. LGTM3 Thanks, Vlad > >

Re: [blink-dev] Intent to Ship: No-Vary-Search Hint for Prerender Speculation Rules

tion to a URL that exactly matches an >in-progress prefetch URL > > The above discussion about No-Vary-Search hint applies to prerender as > well. > > On Thursday, June 6, 2024 at 1:26:34 PM UTC-4 Vladimir Levin wrote: > >> From the explainer, expects_no_vary_search

Re: [blink-dev] Intent to Ship: No-Vary-Search Hint for Prerender Speculation Rules

>From the explainer, expects_no_vary_search helps because when we're prefetching but have not yet received headers, we don't know if that request would match what the user is now navigating to. Do you have a sense of how often the failure cases happen? (ie we waited for that navigation request to

Re: [blink-dev] Re: Intent to Ship: No-Vary-Search support for prerender

LGTM3 On Thu, Jun 6, 2024 at 12:45 PM Chris Harrelson wrote: > LGTM2 > > On Wed, Jun 5, 2024 at 9:56 PM Mike Taylor wrote: > >> LGTM1 - I'm very happy to see this ship. >> On 6/6/24 11:42 AM, Domenic Denicola wrote: >> >> I will abstain from approving this feature as an API Owner, as one of

Re: [blink-dev] Intent to Deprecate and Remove: 0.0.0.0 for Private Network Access

LGTM3 On Wed, Jun 5, 2024 at 11:43 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM2 > > On Wed, Jun 5, 2024 at 5:41 PM Daniel Bratell wrote: > >> LGTM1 >> >> /Daniel >> On 2024-06-03 18:03, 'David Adrian' via blink-dev wrote: >> >> Contact emails l...@chromium.org >> >>

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

like to leave it as a last resort. > > Let me know what you think, and if this sounds acceptable, I can get that > data from UMA to start to inform if we want to pursue the algorithm in (2). > > Thanks, > Dylan > > On Fri, May 31, 2024 at 5:11 AM Vladimir Levin > wrote: > &g

Re: [blink-dev] Re: Intent to Deprecate and Remove: 0.0.0.0 for Private Network Access

On Mon, Jun 3, 2024 at 12:06 PM 'David Adrian' via blink-dev < blink-dev@chromium.org> wrote: > Chrome Status doesn't generate emails for the deprecation trails, only > developer trials, so I've repurposed that here. This is a Finch managed > rollout, not a developer opt-in, due to the extremely

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

On Wed, May 29, 2024 at 5:02 PM 'Dylan Cutler' via blink-dev < blink-dev@chromium.org> wrote: > Hello Blink API Owners, > > > We’re seeking approval to unship and relaunch CHIPS (a.k.a. partitioned > cookies) in Android WebView only. > > Rationale > > The WebViewClient supports a method,

Re: [blink-dev] Re: Intent to Ship: Importmap integrity

LGTM2 On Wed, May 29, 2024 at 11:41 AM Mike Taylor wrote: > LGTM1 > On 5/24/24 3:13 PM, Yoav Weiss (@Shopify) wrote: > > > > On Fri, May 24, 2024 at 7:12 PM Panos Astithas > wrote: > >> >> >> On Wed, May 22, 2024 at 2:16 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> >>>

Re: [blink-dev] Intent to Experiment: Keyboard-focusable scroll containers Opt Out

On Wed, May 29, 2024 at 10:47 AM Daniel Bratell wrote: > That is 7 milestones. > > End at 132 inclusive instead? > Oops, off-by-one strikes again! Yes, 132 inclusive is the right endpoint > /Daniel > On 2024-05-28 18:58, Vladimir Levin wrote: > > LGTM to experiment f

Re: [blink-dev] Intent to Ship: Unrestricted WebUSB (available only to Isolated Web Apps)

On Wed, May 29, 2024 at 9:49 AM Mike Taylor wrote: > LGTM1 to ship this for IWAs only. > On 5/22/24 2:11 PM, Reilly Grant wrote: > > LGTM as an IWA OWNER (3x LGTM from Blink API OWNERS are still required > according to the IWA-specific API launch process >

Re: [blink-dev] Intent to Ship: Deprecation of non-standard declarative shadow DOM serialization

On Tue, May 28, 2024 at 12:30 PM Mason Freed wrote: > > > On Mon, May 27, 2024 at 8:15 AM Vladimir Levin > wrote: > >> Interoperability and Compatibility >>> >>> The use counter for getInnerHTML() ( >>> https://chromestatus.com/metrics/feat

Re: [blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

LGTM3 On Tue, May 28, 2024 at 12:55 PM Ben Kelly wrote: > > On Tue, May 28, 2024 at 10:59 AM Vladimir Levin > wrote: > >> Hey Anton, >> >> Can you please request reviews for the various chips >> [image: chips.png] >> > > Done. Thanks. > > &

Re: [blink-dev] Intent to Experiment: Keyboard-focusable scroll containers Opt Out

to migrate their components, we >> are requesting a Deprecation Trial. This trial (called >> “KeyboardFocusableScrollersOptOut”), when enabled, will disable the >> KeyboardFocusableScrollers feature. To give adequate time, we’d like to let >> this deprecation trial run for

Re: [blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

Hey Anton, Can you please request reviews for the various chips [image: chips.png] Thanks! Vlad On Mon, May 27, 2024 at 3:09 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM2 > > On Fri, May 24, 2024 at 5:53 PM Anton Maliev wrote: > >> I see the concern. The 3P can use

Re: [blink-dev] Intent to Ship: The ServiceWorker static routing API not condition support

On Fri, May 24, 2024 at 3:43 AM Yoshisato Yanagisawa < yyanagis...@chromium.org> wrote: > Contact emails > > yyanagis...@chromium.org > > Explainer > > https://github.com/WICG/service-worker-static-routing-api > > Specification > > https://w3c.github.io/ServiceWorker/#dom-routercondition-not > >

Re: [blink-dev] Intent to Ship: Deprecation of non-standard declarative shadow DOM serialization

On Fri, May 24, 2024 at 7:42 PM Mason Freed wrote: > {Note: I previously sent what should have been an intent to deprecate and > remove for this feature. However, that one failed to make it to the right > dashboards due to the subject line being incorrect. See that prior > conversation right

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

st-013.html both look like minor > differences, but it seems like it only happens on Linux (Chrome) and not > Windows (Edge)? > > > > There are also 3 failing subtests in font-size-adjust-computed.html, > does that depend on resolving one of the spec issues? Or can we match what > Firefox a

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate old CSS custom state syntax

ether the deprecated syntax works or not because the other > browsers didn't have it before and neither did we until a couple years ago. > I meant I hope that existing use is either feature-detected or it's using both properties. In either case, it's very easy to fix if problems arise since a

Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

Deprecation Trial is >>> finished? (Or are you just requesting an Origin Trial to temporarily >>> disable something, and expect it to be re-enabled in the future?) >>> >>> Something that approaches an Explainer would probably be helpful here - >>> thanks! >>> &

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate old CSS custom state syntax

Hey, 0.04% seems like a fairly sizable number. Do you know what the breakage looks like or whether this usage is limited to a library/a small set of large websites or something else? Ideally, this is feature detected with some fallback syntax On Tue, May 21, 2024 at 1:39 PM Joey Arhar wrote:

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

> Thanks. At least two votes for straight-to-100%, so that's what I'll do. > FWIW, I think both strategies have pros and cons, but I do support the straight-to-100% in this case LGTM1 to this plan, while being ready to adapt to things that come up in >>> the proce

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

On Thu, May 16, 2024 at 11:56 AM Mason Freed wrote: > > On Wed, May 15, 2024 at 9:36 PM Vladimir Levin > wrote: > >> I recall that some of this usage was feature detected: if mutation events >> are supported, use them; otherwise, use something else. Unfortunately, th

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

gt;>> It would be nice for the PR to be reviewed and approved, even without >>>>>> other stakeholder support. >>>>>> >>>>>> Additionally - the explainer mentions a few options for feature >>>>>> detection. Any progress on th

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

On Thu, May 16, 2024 at 10:02 AM ChangSeok Oh wrote: > Contact emails > changseok...@bytedance.com, changs...@chromium.org > > Explainer > None > > Specification > https://www.w3.org/TR/css-fonts-5/#font-size-adjust-prop > > Summary > > The font-size-adjust CSS property enhances readability

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

I recall that some of this usage was feature detected: if mutation events are supported, use them; otherwise, use something else. Unfortunately, that makes it difficult to estimate the expected number of breakages. I agree though that it would be nice to understand the type of usage that still

Re: [blink-dev] Intent to Ship: Multi-argument alt text in CSS Generated Content

On Mon, May 13, 2024 at 2:23 PM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > *Contact emails* > > dan...@microsoft.com > > *Explainer* > > None > > *Specification* > > > https://drafts.csswg.org/css-content-3/#valdef-content---string--counter--attr > and

Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

On Fri, May 10, 2024 at 2:40 PM mark a. foltz wrote: > Contact emailsmfo...@chromium.org, bryantchand...@chromium.org > > ExplainerNone > > Specification > https://docs.google.com/document/d/1ZnX2JROjr9l4y2_OPMpfVlLOo-A5cQzD4mWarj9kXQ0/edit > > Design docs > >

Re: [blink-dev] Intent to Experiment: Keyboard-focusable scroll containers Opt Out

On Fri, May 10, 2024 at 2:18 PM Mike Taylor wrote: > Is there a chromestatus entry associated with this intent? There's a lot > of information missing from this Intent (see > https://groups.google.com/a/chromium.org/g/blink-dev/c/LwgSKPBivuM/m/0dRsXWhBAgAJ > as what is typical) - could you reply

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

ps (i.e., the user >agent has a "popup blocker" enabled) > - The user agent may inform the user that a popup has been blocked. > > > On Thursday, May 9, 2024 at 7:30:09 AM UTC-7 Vladimir Levin wrote: > >> On Wed, May 8, 2024 at 7:46 PM Mike Wasserman

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

On Wed, May 8, 2024 at 7:46 PM Mike Wasserman wrote: > Contact emails > > m...@chromium.org, fugu-...@chromium.org > > Explainer > > https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture > > Specification > > https://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen

Re: [blink-dev] Unable to write Serialized SkPicture into a File

Hey Steven, The path to convert information necessary for rendering into SkPictures may or may not exist in the Chromium codebase, but it's certainly not actively maintained or developed. Ultimately all information is available, but it may come from several different sources. For images, for

Re: [blink-dev] Intent to Ship: Support Cross-Origin Shared Storage Worklets

On Fri, Apr 19, 2024 at 12:52 PM Yao Xiao wrote: > *Contact emails* > cam...@chromium.org > jkar...@chromium.org > yao...@chromium.org > rohitgu...@google.com > ashame...@google.com > > *Explainer* > https://github.com/WICG/shared-storage > > *Specification* >

Re: [blink-dev] Intent to Ship: Declarative shadow DOM serialization

On Thu, Apr 4, 2024 at 6:54 PM Mason Freed wrote: > Contact emailsmas...@chromium.org > > Explainer > https://github.com/whatwg/html/issues/8867#issuecomment-1856696628 > > Specificationhttps://html.spec.whatwg.org/#dom-element-gethtml > > Summary > > The prototype implementation (which was

Re: [blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

On Thu, Apr 4, 2024 at 12:19 PM 'Russ Hamilton' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > pauljen...@chromium.org, behamil...@google.com > > Explainer > > Chrome: > https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md > > Services: >

Re: [blink-dev] Intent to Prototype: Document-Isolation-Policy

bility with just spamming 3p iframes but that likely exists today anyway Thanks! Vlad > > Charlie > > On Thu, Apr 4, 2024 at 8:05 AM Vladimir Levin wrote: > >> This does sound a bit unfortunate. My understanding is that at least this >> behavior is deterministic, right

Re: [blink-dev] Intent to Prototype: Document-Isolation-Policy

This does sound a bit unfortunate. My understanding is that at least this behavior is deterministic, right? That is, either the same-origin frames will be able to script each other or they won't and this will happen consistently (based on the agent cluster key). An observation I had is that it

Re: [blink-dev] Capture Skia Commands From Chromium

Hey Steven, I don't think there is any way you would be able to get the Skia commands without modifying the code. Traces don't typically contain the necessary draw commands. There are a few places you can get those commands, mostly in the cc directory, or thereabouts. I recommend watching Life

Re: [blink-dev] Intent to Ship: View Transitions: transition types

; >>> LGTM1 >>> >>> On Thursday, November 9, 2023 at 7:05:57 PM UTC+1 Vladimir Levin wrote: >>> >>> >>> >>> On Thu, Nov 9, 2023, 12:54 Mike Taylor wrote: >>> >>> On 11/8/23 3:53 PM, Vladimir Levin wrote: >>> >

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

On Mon, Mar 18, 2024 at 11:17 AM 'Simon Hangl' via blink-dev < blink-dev@chromium.org> wrote: > Hello blink-dev, > > We’d like to ask for an extension to our Origin Trial, from M124 to M130. > This is due to a dependency on isolated web apps, which are delayed. > The intent process only allows

[blink-dev] Intent to Ship: CSS view-transition-class and class VT argument syntax

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-classes.md Specification https://drafts.csswg.org/css-view-transitions-2/#view-transition-class-prop Summary This feature introduces a new CSS

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

On Mon, Mar 11, 2024 at 1:42 PM Aaron Selya wrote: > Contact emails > > se...@chromium.org, dylancut...@chromium.org, kaustub...@chromium.org > > > Explainer > > Keying of "CHIPS" cookies should align with other state: > > >

Re: [blink-dev] Intent to Ship: Compute Pressure

Asking as a user, the spec draft recommends that user agents... ... show some form of user-visible notification that informs the user when > a pressure observer is active, as well as provides the user with the means > to block the

[blink-dev] Re: Intent to Ship: Document Render-Blocking

Re failing tests: The flag is currently in "test" status which I don't believe would be picked up by wpt.fyi

[blink-dev] Intent to Ship: Document Render-Blocking

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/WICG/view-transitions/blob/main/document-render-blocking.md#blocking-element-id Specification https://html.spec.whatwg.org/multipage/links.html#link-type-expect Summary This feature enables authors to block

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

On Wed, Feb 21, 2024 at 11:25 AM Dustin Mitchell wrote: > Thanks for the comments! > > On Tue, Feb 20, 2024 at 11:10 AM Vladimir Levin > wrote: > >> >> >> On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev < >> blink-dev@chrom

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsdjmit...@chromium.org > > Explainer > https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.md > >

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

On Mon, Feb 19, 2024 at 12:10 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Fri, Feb 16, 2024 at 8:19 PM Brad Triebwasser > wrote: > >> Usage for the legacy permission and permission policy are ~0.006 >> and

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

On Wed, Feb 14, 2024 at 1:53 PM Jeffrey Yasskin wrote: > Non-API-owner opinions inline: > > On Wed, Feb 14, 2024 at 1:42 PM 'Vladimir Levin' via blink-dev < > blink-dev@chromium.org> wrote: > >> I just had some clarifying questions >> >> On Wed, Fe

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

I just had some clarifying questions On Wed, Feb 14, 2024 at 1:13 PM Joey Arhar wrote: > Some additional notes: > - This API is tested in the declarative ShadowDOM tests in interop2024, > and it is counting against us to not have it enabled by default. > - The future sanitization options will

Re: [blink-dev] Intent to Ship: ServiceWorker static routing API

On Thu, Feb 8, 2024, 22:56 Yoshisato Yanagisawa wrote: > Contact emails > > yyanagis...@chromium.org, sisidov...@chromium.org > > Explainer > > https://github.com/WICG/service-worker-static-routing-api > > Specification > > https://github.com/w3c/ServiceWorker/pull/1701 > > Summary > > This API

Re: [blink-dev] Request for Deprecation Trial: Deprecate Mutation Events

On Thu, Feb 1, 2024 at 6:30 PM Mason Freed wrote: > > On Thu, Feb 1, 2024 at 7:12 AM Vladimir Levin wrote: > >> This is very exciting! Thank you for working on this. >> > > Thanks! > > >> Do you know whether the existing usage is feature checked? 1.58%

Re: [blink-dev] Request for Deprecation Trial: Deprecate Mutation Events

On Wed, Jan 31, 2024 at 8:54 PM Mason Freed wrote: > Contact emailsmas...@chromium.org > > ExplainerNone > > Specificationhttps://w3c.github.io/uievents/#legacy-event-types > > Summary > > Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, > `DOMNodeRemoved`,

Re: [blink-dev] Intent to Ship: Element Reflection

On Wed, Jan 31, 2024 at 6:14 PM Alice Boxhall wrote: > > > On Thursday, February 1, 2024 at 6:52:13 AM UTC+11 vmp...@google.com > wrote: > > On Wed, Jan 31, 2024 at 10:10 AM alice wrote: > > Contact emails > al...@igalia.com, mere...@chromium.org > > Explainer > >

Re: [blink-dev] Intent to Ship: Element Reflection

On Wed, Jan 31, 2024 at 10:10 AM alice wrote: > Contact emails > al...@igalia.com, meredi...@chromium.org > > Explainer > > https://github.com/WICG/aom/blob/gh-pages/aria-reflection-explainer.md#reflecting-element-references > > Specification > >

Re: [blink-dev] Intent to Ship: Private Network Access permission to relax mixed content

On Fri, Jan 26, 2024 at 5:07 AM 'Yifan Luo' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails...@chromium.org, cl...@chromium.org > > Explainer > https://github.com/WICG/private-network-access/blob/main/permission_prompt/explainer.md > >

Re: [blink-dev] Intent to Ship: NavigationActivation

On Fri, Jan 26, 2024 at 4:27 AM Noam Rosenthal wrote: > Contact emailsjap...@chromium.org, nrosent...@chromium.org > > Explainer > https://github.com/WICG/view-transitions/blob/main/navigation-activation-explainer.md > > Specification >

Re: [blink-dev] Intent to Deprecate non-standard declarative shadow DOM serialization

On Fri, Jan 19, 2024 at 7:54 PM Mason Freed wrote: > > > On Friday, January 19, 2024 at 12:27:50 PM UTC-8 vmp...@google.com wrote: > > Interoperability and Compatibility > > The use counter for getInnerHTML() (https://chromestatus.com/ > metrics/feature/timeline/popularity/3874) shows 0.04% of

[blink-dev] Intent to Prototype: CSS view-transition-class and class VT argument syntax

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-classes.md Specificationhttps://drafts.csswg.org/css-view-transitions-2 Summary This feature introduces a new CSS property view-transition-class

Re: [blink-dev] New API owner: Domenic Denicola

Congrats, Domenic! On Fri, Jan 19, 2024 at 3:59 PM Rick Byers wrote: > Hi blink-dev, > +Domenic Denicola has volunteered to donate his > time and considerable web platform expertise to reviewing intent threads as > an API owner. Domenic is very active in the web standards community > including

Re: [blink-dev] Intent to Deprecate non-standard declarative shadow DOM serialization

On Fri, Jan 19, 2024 at 3:13 PM Mason Freed wrote: > Contact emailsmas...@chromium.org > > Explainer > https://github.com/whatwg/html/issues/8867#issuecomment-1856696628 > > SpecificationNone > > Summary > > The prototype implementation (which was shipped in 2020 and then > shape-changed in

Re: [blink-dev] Intent to Ship: RTCRtpSender setParameters() extensions for requesting the generation of a key frame

Thank you for the detailed explanation. It's hard to decipher from meeting notes whether a discussion is bikeshedding or serious objections :) Based on your description, it does seem like there is good consensus Thanks, Vlad On Fri, Jan 19, 2024 at 5:14 AM Henrik Boström wrote: > Having

Re: [blink-dev] Intent to Ship: RTCRtpSender setParameters() extensions for requesting the generation of a key frame

Based on the WG discussion (meeting notes: https://www.w3.org/2023/05/16-webrtc-minutes.html#t04) it didn't seem that there is a very strong consensus that this is a right spot to add an extra parameter. There are also no signals on the RFPs, but the spec PR has landed. How would you assess the

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

On Thu, Jan 11, 2024 at 6:08 PM 'Sahir Vellani' via blink-dev < blink-dev@chromium.org> wrote: > Hi all, good news! > > Reviving this thread because we have accomplished: > 1. TAG Review Completion: Extending the PointerEvent with Unique > DeviceId Attribute · Issue #880 · w3ctag/design-reviews

Re: [blink-dev] Intent to Ship: Set methods

On Tue, Jan 2, 2024 at 1:51 PM Rezvan Mahdavi Hezaveh wrote: > Contact emailsrez...@chromium.org, s...@chromium.org > > ExplainerNone > > Specificationhttps://tc39.es/proposal-set-methods > > Summary > > Set methods are new methods like union and intersection that are added to > JavaScript's

Re: [blink-dev] PSA: Changing File System Access API interaction with the back/forward cache

ache to allow the active page to open > the writable. > > On Thu, Dec 21, 2023, 8:23 AM Vladimir Levin wrote: > >> >> >> On Wed, Dec 20, 2023 at 8:17 PM 'Nathan Memmott' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Howdy blink-dev, >>>

Re: [blink-dev] PSA: Changing File System Access API interaction with the back/forward cache

On Wed, Dec 20, 2023 at 8:17 PM 'Nathan Memmott' via blink-dev < blink-dev@chromium.org> wrote: > Howdy blink-dev, > > In Chromium M121, we will update how the File System Access (FSA) API > interacts with the back/forward cache (BFCache). This should only affect > the conditions a page can

Re: [blink-dev] Intent to Ship: WebGL drawingBufferStorage

On Mon, Nov 27, 2023 at 4:20 PM 'Christopher Cameron' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsccame...@chromium.org > > ExplainerNone > > Specificationhttps://github.com/KhronosGroup/WebGL/pull/3222 > > Summary > > WebGL allows rendering into textures and renderbuffers of

Re: [blink-dev] Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

On Mon, Dec 11, 2023 at 6:05 PM 'Anupam Snigdha' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org > > Specification > > > https://w3c.github.io/clipboard-apis/#dom-clipboard-write > > Design docs > > >

Re: [blink-dev] Web-Facing Change PSA: align-content CSS property for blocks

On Mon, Dec 11, 2023 at 10:10 PM 一丝 wrote: > WebKit is being actively implemented: > https://github.com/WebKit/WebKit/pull/21522 > > 以上 > 一丝 > > > PhistucK 于2023年12月12日周二 07:50写道： > >> > Low risk. This just expands coverage of a CSS property. >> >> Well... Not that low, perhaps? >> I think I

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

On Wed, Dec 6, 2023 at 1:16 AM 'Fergal Daly' via blink-dev < blink-dev@chromium.org> wrote: > > > On Wed, 6 Dec 2023 at 13:55, Fergal Daly wrote: > >> On Wed, 6 Dec 2023 at 12:29, Vladimir Levin wrote: >> >>> Thank you for the update! >>> >

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

this change. Thanks everyone, > > F > > On Thu, 16 Nov 2023 at 13:37, Fergal Daly wrote: > >> Thanks everyone. Yes we will keep this thread up to date before releasing >> this (we'll go to canary/dev very soon so that we start getting stability >> and impact signal

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

ium.org/p/chromium/issues/detail?id=1468438> further >>>> reduce the risk such that we believe it is unlikely that this will lead to >>>> new security issues. >>>> >>>> On Friday, October 13, 2023 at 7:14:46 AM UTC-7 vmp...@chromium.org >>>> w

Re: [blink-dev] Intent to Ship: View Transitions: transition types

On Thu, Nov 9, 2023, 12:54 Mike Taylor wrote: > On 11/8/23 3:53 PM, Vladimir Levin wrote: > > Contact emails vmp...@chromium.org, nrosent...@chromium.org > > Explainer > https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-types.md > &g

[blink-dev] Intent to Ship: View Transitions: transition types

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-types.md Specification https://drafts.csswg.org/css-view-transitions-2/#the-active-view-transition-pseudo Summary This feature allows View

[blink-dev] Intent to Ship: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

Contact emailsvmp...@chromium.org ExplainerNone Specification https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility Summary This feature adds three more values to the checkVisibility ( https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility) dictionary members: *

[blink-dev] Intent to Prototype: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

Contact emailsvmp...@chromium.org Specification https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility Summary This feature adds three more values to the checkVisibility ( https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility) dictionary members: * opacityProperty as an

  1   2   >