Re: [blink-dev] Intent to Ship: Zstd Content-Encoding

Thanks for working on this!! This is extremely exciting! On Tue, Feb 13, 2024 at 1:11 AM Nidhi Jaju wrote: > Contact emails > > nidhij...@chromium.org > > Explainer > > > https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/edit?usp=sharing > > Specification > >

Re: [blink-dev] Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

LGTM1 On Thursday, February 1, 2024 at 8:42:36 PM UTC+9 Koji Ishii wrote: > Hi Philip, thanks for the questions. Please see replies inline: > > Thanks for linking the tests, judging just by the test names it looks like >> many combinations of languages and fonts are tested. >> > > Yes, many

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Just started using the origin trial in one of our apps that requires a slightly overly extertive lift to change from webSQL to IndexedDB. The expiry says May 28, 2024 -- what is the potential that date could be extended while we work to release our new version? On Friday, September 8, 2023 at

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

Thanks Nan for helping us better understand the feature. LGTM1 given the following "...it’s possible that Android may ship support for new registration fields in the OS-level API, which may or may not be supported in the web API. The web API may lag behind, or even not implement the new

[blink-dev] Intent to Ship: Zstd Content-Encoding

Contact emails nidhij...@chromium.org Explainer https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/edit?usp=sharing Specification https://datatracker.ietf.org/doc/html/rfc8878 Design docs

[blink-dev] Intent to Ship: Document picture-in-picture: allow Window's focus() API to focus opener

Contact emailsstei...@chromium.org, liber...@chromium.org ExplainerNone Specificationhttps://github.com/WICG/document-picture-in-picture/pull/109 Summary This enables `opener.focus()` from a document picture-in-picture window to bring system-level focus to the tab that owns the document

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

On Monday, February 12, 2024 at 4:53:50 PM UTC+2 mike...@chromium.org wrote: On 2/12/24 6:36 AM, Eldar Rello wrote: Contact emails eldar...@gmail.com Explainer None Specification https://w3c.github.io/webrtc-extensions/#dom-rtcrtpreceiver-jitterbuffertarget Summary JitterBufferTarget

Re: [blink-dev] Intent to Ship: CSS paint-order for non-SVG text

Done (requested N/A). On Mon, Feb 12, 2024 at 3:05 AM Manuel Rego Casasnovas wrote: > Oops, before we can approve you have to fill the other review gates at > chromestatus, e.g. > https://chromestatus.com/feature/5178467903864832?gate=5166816630669312 > > Could you make sure you request the

[blink-dev] Intent to Ship: RTCIceCandidate url and relayProtocol attributes

Contact emails phan...@microsoft.com Explainer None Specification https://w3c.github.io/webrtc-pc/#rtcicecandidate-interface Summary https://w3c.github.io/webrtc-pc/#rtcicecandidate-interface gets implementations for two new properties for RTCIceCandidate objects emitted from the

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

I've made some changes to address the loss of styles and other formatting issues during write. During read, if the authors have added `image/svg+xml` to the

[blink-dev] Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

[blink-dev] Web-Facing Change PSA: InputDeviceInfo.getCapabilities() for unavailable devices

Contact emailsgui...@chromium.org Specification https://w3c.github.io/mediacapture-main/#ref-for-dom-inputdeviceinfo-getcapabilities-1 Design docs https://docs.google.com/document/d/1gwAF4qMXvHLQH-Fb6MxOgiSxXzK47AwiVPvnvJIccaE/r/0-T1AP5YsdFksujPUY7rJV1Q/edit?tab=t.0 Summary Make

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

We also need to flip the various review gates on the chromestatus entry (privacy, security, enterprise... etc.). If you're working with someone at Google on this feature, perhaps they could assist? On 2/12/24 9:53 AM, Mike Taylor wrote: On 2/12/24 6:36 AM, Eldar Rello wrote:

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

On 2/12/24 6:36 AM, Eldar Rello wrote: Contact emails eldar.re...@gmail.com Explainer None Specification https://w3c.github.io/webrtc-extensions/#dom-rtcrtpreceiver-jitterbuffertarget Summary JitterBufferTarget attribute allows applications to specify

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

I think deviceProperties is reasonable. The other question was when deviceId would be populated? E.g. should touches on the same touchscreen device have the same deviceId or should we only have a deviceId when we can uniquely identify the particular pointer? I suspect maybe the latter since

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

Agree that the risk feels low... one thing to perhaps check for (if you have UKM or use counters) is to see if there is any legit usage on sites of `navigator.permissions.query()` that isn't catching errors, since that will throw a TypeError and can break a page. On 2/12/24 9:16 AM, Rick

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

Presumably the risk of legitimate breakage here is bounded by the use of the Window Management API, right? Are there any UseCounters for the various Window Management operations? I couldn't find any at a quick glance. I imagine legitimate usage is dominated by a few sites with an obvious need (do

[blink-dev] Intent to Ship: jitterBufferTarget

Contact emailseldar.re...@gmail.com ExplainerNone Specification https://w3c.github.io/webrtc-extensions/#dom-rtcrtpreceiver-jitterbuffertarget Summary JitterBufferTarget attribute allows applications to specify a target duration of time in milliseconds of media for the RTCRtpReceiver's jitter

Re: [blink-dev] Intent to Ship: CSS paint-order for non-SVG text

Oops, before we can approve you have to fill the other review gates at chromestatus, e.g. https://chromestatus.com/feature/5178467903864832?gate=5166816630669312 Could you make sure you request the review for all the gates: Privacy, Security, Enterprise, Debuggability and Testing? Thanks!

Re: [blink-dev] Intent to Ship: CSS paint-order for non-SVG text

LGTM1. Good to know it's a different issue in Firefox. Now that all browsers will be supporting this, please could you make the test non tentative? JFYI, I've filled an issue so the MDN documentation gets updated to also include the HTML case: https://github.com/mdn/content/issues/32236