[blink-dev] Intent to Implement and Ship: Update of "xml" prefix handling in lookupNamespaceURI() and createNSResolver()

Contact emailstk...@chromium.org ExplainerNone Specificationhttps://dom.spec.whatwg.org/#locate-a-namespace https://dom.spec.whatwg.org/#dom-xpathevaluatorbase-creatensresolver Summary Node.lookupNamespceURI() supports "xml" and "xmlns" prefixes by default. The function returns fixed namespace

[blink-dev] Intent to Ship: 'display' property with multiple values

Contact emailstk...@chromium.org ExplainerNone Specification https://w3c.github.io/csswg-drafts/css-display/#the-display-properties Design docs Summary CSS 'display' property supports two or three keywords. Web authors can specify - How the box and its neighbor boxes are located; inline or bloc

Re: [blink-dev] Re: Intent to Implement & Ship: User-Agent Reduction Phase 6 (deviceModel and androidVersion reduction in Android)

Hi blink-dev, UA Reduction Phase 6 is ramping up to 50% of the stable release population today. Thanks. Victor On Tuesday, April 4, 2023 at 2:04:37 PM UTC-4 Victor Tan wrote: > Hi blink-dev, > UA Reduction Phase 6 is currently ramping up to 10% of the stable release > population. > > Thank

[blink-dev] Re: Intent to Prototype: Disabling UA transitions on same-document navigations

FYI, I added a visual example to the problem statement to clarify the current status. On Fri, Apr 21, 2023, 7:54 PM Khushal Sagar wrote: > Contact emailskhushalsa...@google.com, liuwill...@google.com

[blink-dev] FYI: HSTS preload enforcing continued requirements

Hi folks, This is a heads-up that the HSTS preload list (https://hstspreload.org) has started enforcing its requirements that domains maintain their preload eligibility after enrollment. While these requirements have always been present, we haven'

Re: [blink-dev] Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs

I share the concerns around compat risk and making the platform less predictable for businesses. But I also don't see any alternative given that at least Google Chrome is going ahead with strong tracking protection and Firefox and Safari already have this. I assume the codebase will support both pa

Re: [blink-dev] Intent to Implement and Ship: Remove Secure Payment Confirmation user activation requirement

LGTM3 On 4/25/23 11:05 AM, Yoav Weiss wrote: LGTM2 On Tue, Apr 25, 2023 at 4:15 PM Rick Byers wrote: This is a small behavior change to a shipped feature with no explicit API exposure. LGTM1 On Wed, Apr 19, 2023 at 2:05 PM Nick Burris wrote: Le mercredi 19 avril 2

Re: [blink-dev] Intent to Implement and Ship: Remove Secure Payment Confirmation user activation requirement

LGTM2 On Tue, Apr 25, 2023 at 4:15 PM Rick Byers wrote: > This is a small behavior change to a shipped feature with no explicit API > exposure. LGTM1 > > On Wed, Apr 19, 2023 at 2:05 PM Nick Burris wrote: > >> >> >> Le mercredi 19 avril 2023 à 03 h 45 min 37 s UTC-4, Yoav Weiss a écrit : >> >>

Re: [blink-dev] Intent to Ship: Private Network Access preflight requests for subresources

Titouan, Excellent. Since I am now subscribed to this blog, I will be aware of these changes. ( although google SSO used my personal email, not my employer) I was (and still am) cautious about getting ALL the changes, since I'm sure there are hundreds. And our little embedded web server does

Re: [blink-dev] Intent to Ship: Partitioning Storage, Service Workers, and Communication APIs

On 4/24/23 2:11 PM, Yoav Weiss wrote: Apologies for my slowness! On Thu, Apr 6, 2023 at 2:01 AM Mike Taylor wrote: On 4/4/23 11:51 PM, Yoav Weiss wrote: Thanks for working on this!! Aligning with Safari and Firefox on this means that this is important not just for user priva

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

Hi Joey, I'm excited for this to ship. I see that there's some feedback from the TAG and concern from the WG about at least one open spec issue. Please let us know here when you feel that either

Re: [blink-dev] Intent to Implement and Ship: Remove Secure Payment Confirmation user activation requirement

This is a small behavior change to a shipped feature with no explicit API exposure. LGTM1 On Wed, Apr 19, 2023 at 2:05 PM Nick Burris wrote: > > > Le mercredi 19 avril 2023 à 03 h 45 min 37 s UTC-4, Yoav Weiss a écrit : > > On Mon, Apr 17, 2023 at 9:42 PM Nick Burris wrote: > > Contact emailsnb

Re: [blink-dev] Intent to Ship: Private Network Access preflight requests for subresources

[blink-dev@ to bcc] Hi Scott, Thanks for reaching out. Answers inline below. On Mon, Apr 24, 2023 at 9:32 PM Scott Weber wrote: > Grammar correction, sorry: > "a brief tutorial to a newbie on *the status of* PNA and..." > > On Monday, April 24, 2023 at 2:13:59 PM UTC-5 Scott Weber wrote: > >>

Re: [blink-dev] Intent to Ship: Private State Tokens API

Thanks Eric! A couple of issues Martin Thomson filed and I don't think were addressed are #232 and #230 . It'd be good to address them in some way. I also noticed that a bunch of issues were ad

[blink-dev] Intent to Ship: Resource Timing: Expose interim response times

Contact emailsnrosent...@chromium.org Specificationhttps://github.com/w3c/resource-timing/pull/366 Summary Expose timings about final response headers start/end and response body time. Requested by people who use RT-based dashboards as a consequence of 103 Early hints. Blink componentBlink>Per

[blink-dev] Intent to ship: VisibilityStateEntry

Contact emails...@chromium.org, nrosent...@chromium.org Explainer https://docs.google.com/document/d/1l5kHiJRkdQwEN-CYI5_mUNODhQVB5rCyjN4jHDdXDHA/edit# Specificationhttps://github.com/whatwg/html/pull/8206 Summary Exposes to PerformanceObserver the initial visibility state of a page plus any vi