Re: [blink-dev] Intent to Ship: ::scroll-marker and ::scroll-marker-group for Carousel, ::column pseudo element for Carousel and ::scroll-button() pseudo elements

2025-03-04 Thread Xiaocheng Hu
(With my TAG hat on) Could the shipping of this feature be held until 3/18? We have discussed the Carousel-related features at the TAG F2F and have some concerns. We've invited

Re: [External] Re: [blink-dev] Re: Intent to Ship: H26x Codec support updates for MediaRecorder

2025-03-04 Thread '朱思达' via blink-dev
Given your example, it seems like `video/mp4;codecs="hev1.1.6.L120.90"` is supported by Chrome but not Safari, while the opposite is true for `video/mp4;codecs="hvc1"`. AFAIK, Safari doesn't support HEVC MediaRecorder encoding. If you are talking about decoding, for decoding, safari supports both

Re: [blink-dev] Intent to Ship: CSS interactivity

2025-03-04 Thread Xiaocheng Hu
(With my TAG hat on) Could the shipping of this feature be held until 3/18? We have discussed the Carousel-related features at the TAG F2F and have some concerns. We've invited

[blink-dev] Intent to Prototype: CSS sibling-index() and sibling-count()

2025-03-04 Thread Chromestatus
Contact emails futh...@chromium.org, se...@chromium.org Explainer https://github.com/w3c/csswg-drafts/blob/main/css-values-5/tree-counting-explainer.md Specification https://drafts.csswg.org/css-values-5/#tree-counting Summary sibling-index() and sibling-count() can be used as integers in CS

Re: [blink-dev] Implement and Ship: Blob URL Partitioning: Fetching/Navigation

2025-03-04 Thread Andrew Williams
Hi everyone, Quick update on this. We landed a new use counter implementation last week that better gauges actual breakage, and preliminary data from Chrome Canary shows that no instances of breakage were detected except for a few from yesterday, and those likely correspond to me running the parti

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread Mason Freed
Thanks Jason! Here's the new/updated email: Contact emailsmas...@chromium.org ExplainerNone SpecificationNone Design docs https://github.com/whatwg/html/issues/7867#issue-1218728578 Summary The HTML spec contains a list of special rules for tags nested within , , , or tags: https://html.spe

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread 'Jason Robbins' via blink-dev
The kicker: the chromestatus tool only gives you one shot at creating the intent email. Now that I've done it once, that button is gone. In order to send another email, it seems that I'd have to create an entirely new chromestatus entry, and I'm loath to do that. Let me know if it's enough to

[blink-dev] Intent to Prototype: Full frame rate render blocking attribute

2025-03-04 Thread Chromestatus
Contact emails g...@google.com Explainer https://github.com/whatwg/html/issues/11070 Specification None Summary We propose to add a new render blocking token full-frame-rate to the blocking attributes. When the renderer is blocked with the full-frame-rate token, the renderer will work at a

[blink-dev] Intent to Ship: CSS anchor positioning remembered scroll offset

2025-03-04 Thread Morten Stenshorne
Contact emailsmsten...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-anchor-position-1/#scroll Summary Add support for the concept of "remembered scroll offset" - see https://drafts.csswg.org/css-anchor-position-1/#scroll When a positioned element has a default anchor, an

Re: [External] Re: [blink-dev] Re: Intent to Ship: H26x Codec support updates for MediaRecorder

2025-03-04 Thread Philip Jägenstedt
Thank you Sida for that breakdown, it's good to know we're not overlooking any encoding or decoding surface. The most important question here is the one of royalty-free codecs vs non-RF codecs, and the API owners will discuss this again alongside the WebRTC intent. Poking a bit at the details, ho

[blink-dev] Re: Intent to Ship: H265 (HEVC) codec support in WebRTC

2025-03-04 Thread Henrik Boström
AV1 is great from a quality perspective, but it is not an option for use cases that require hardware acceleration. Diego mentioned potential server-side requirements, on the client-side estimates are only 8% Windows endpoints and 0% macOS endpoints have HW accelerated AV1 support. For mobile cl

[blink-dev] Intent to Ship: Language support for CanvasTextDrawingStyles

2025-03-04 Thread Chromestatus
Contact emails schen...@chromium.org Explainer https://github.com/whatwg/html/pull/10873 Specification https://github.com/whatwg/html/pull/10873 Summary The DOM element, like all DOM elements, accepts a `lang` attribute that is used to define language specific treatment for font selection

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread Mason Freed
Yep, sorry about the missing fields - I noticed a few of those after sending the initial intent. I just updated the rest, see below for some comments: On Mon, Mar 3, 2025 at 5:01 PM Domenic Denicola wrote: > This Intent is missing a lot of fields we usually require: > >- Explainer > > No exp

Re: [blink-dev] Intent to Ship: CSS interactivity

2025-03-04 Thread Rick Byers
Hi Xiaocheng, Thank you for digging in and scheduling time with Rob to discuss further. However our policy is not to delay launching features based on a desire for review and discussion beyond one month from the point

Re: [blink-dev] Intent to Ship: ::scroll-marker and ::scroll-marker-group for Carousel, ::column pseudo element for Carousel and ::scroll-button() pseudo elements

2025-03-04 Thread Rick Byers
[Repeating the same response as in the other carousel feature ] Hi Xiaocheng, Thank you for digging in and scheduling time with Rob to discuss further. However our policy

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread 'Jason Robbins' via blink-dev
Oh, and to clarify, I was suggesting that you could copy using the small copy-icon button and paste it on this thread as a reply. Don't start a new blink-dev thread or use the "Post directly to blink-dev" button (because that will start a new thread). Thanks, jason! On Tuesday, March 4, 2025

[blink-dev] Re: Intent to Ship: Language support for CanvasTextDrawingStyles

2025-03-04 Thread Vladimir Levin
On Tuesday, March 4, 2025 at 11:17:42 AM UTC-5 Chromestatus wrote: Contact emails schen...@chromium.org Explainer https://github.com/whatwg/html/pull/10873 Specification https://github.com/whatwg/html/pull/10873 Summary The DOM element, like all DOM elements, accepts a `lang` attribute

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread Vladimir Levin
Re TAG: I don't believe we need a TAG review for deprecations or removals. On Tuesday, March 4, 2025 at 8:54:00 PM UTC-5 Domenic Denicola wrote: Thanks very much Mason (and Jason). It wasn't clear to me that this was just in the initial "deprecate" stage, not the "remove" stage: I wish Chrome

[blink-dev] Re: Intent to Ship: PaymentRequest on WebView

2025-03-04 Thread Vladimir Levin
I believe this was the intent for non-WebView PaymentRequest: https://groups.google.com/a/chromium.org/g/blink-dev/c/p1DYoxHlkKg/m/rBqBMGbFCgAJ LGTM1 to ship to WebView as well with the restriction you outlined. Please also start the rest of the reviews (WP Security, Enterprise, Testing). O

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements

2025-03-04 Thread Domenic Denicola
Thanks very much Mason (and Jason). It wasn't clear to me that this was just in the initial "deprecate" stage, not the "remove" stage: I wish ChromeStatus tooling separated those more cleanly (like it does Dev Trial vs. Ship). Given that you're still in the preparatory deprecation stage, this leve

Re: [blink-dev] Implement and Ship: Blob URL Partitioning: Fetching/Navigation

2025-03-04 Thread Domenic Denicola
On Wed, Mar 5, 2025 at 2:35 AM Andrew Williams wrote: > Hi everyone, > > Quick update on this. We landed a new use counter implementation last week > that better gauges actual breakage, and preliminary data from Chrome Canary > shows that no instances of breakage were detected except for a few fr