Re: [blink-dev] Re: Intent to Ship: Local Network Access allowing same-origin fetches to potentially trustworthy origins

LGTM3 On Thu, Apr 27, 2023 at 7:14 AM Mike Taylor wrote: > LGTM2 (sorry for the delay, it seems this fell out of our review queue). > On 4/27/23 9:56 AM, Jonathan Hao wrote: > > Hi Yoav, > > It's been 2 weeks but no other API owners have replied. Do you know if > there's any blockers? Should

[blink-dev] Intent to Ship: Keyboard-focusable scroll containers

Contact emailsh...@chromium.org, xiaoche...@chromium.org, dizha...@chromium.org ExplainerNone Specification None Design docsNone Summary Improves accessibility by making scroll containers focusable using sequential focus navigation. Today, the tab key doesn't focus scrollers unless tabIndex

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

Thanks all! FYI we are going to push this back a milestone to target M115 to spend more time investigating improved spam mitigations (see design doc security section). Le mardi 25

[blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

The reason is if your website is fast you don't need to buy CDN and Akamai (and the like) looses money. All this technical reasoning is false. Also fake are the statistics about saying nobody uses push. How could Akamai actually know how much traffic my site does with push? They simply can't.

Re: [blink-dev] Questions related to Layout and Fragment Tree

You can access the fragments via. LayoutBox::PhysicalFragments() . Note there may be more than one if the box has been fragmented (a child within a "columns: 2" element). The easiest way to see the resulting fragment tree is via: ShowFragmentTree() -

[blink-dev] Questions related to Layout and Fragment Tree

Since I'm new to blink I wanted to know how do we obtain the immutable fragment tree from the layout tree.What methods facilates this. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from

Re: [blink-dev] Intent to ship: VisibilityStateEntry

Hooray! Excited to see this landing. On Thu, Apr 27, 2023 at 7:29 AM Mike Taylor wrote: > LGTM2 > On 4/27/23 2:44 AM, Yoav Weiss wrote: > > LGTM1 > > Please send a webkit position for this, even if it is non-blocking. > > > On Wed, Apr 26, 2023 at 5:53 PM Noam Rosenthal > wrote: > >> >> >> On

Re: [blink-dev] Intent to ship: VisibilityStateEntry

LGTM3 On Thu, Apr 27, 2023 at 7:29 AM Mike Taylor wrote: > LGTM2 > On 4/27/23 2:44 AM, Yoav Weiss wrote: > > LGTM1 > > Please send a webkit position for this, even if it is non-blocking. > > > On Wed, Apr 26, 2023 at 5:53 PM Noam Rosenthal > wrote: > >> >> >> On Wed, Apr 26, 2023 at 1:28 PM

[blink-dev] Re: Intent to Implement and Ship: isSecurePaymentConfirmationAvailable API

Le jeudi 20 avril 2023 à 12 h 58 min 34 s UTC-4, Nick Burris a écrit : Contact emailsnbur...@chromium.org, smcgr...@chromium.org, i...@chromium.org Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/233 Design docshttps://docs.google.com/document/d/10zFazJRJMwNLKmH-

Re: [blink-dev] Intent to ship: VisibilityStateEntry

LGTM2 On 4/27/23 2:44 AM, Yoav Weiss wrote: LGTM1 Please send a webkit position for this, even if it is non-blocking. On Wed, Apr 26, 2023 at 5:53 PM Noam Rosenthal wrote: On Wed, Apr 26, 2023 at 1:28 PM Yoav Weiss wrote: Thanks for pushing this over the line!!

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

On Wed, Apr 26, 2023 at 2:02 PM Mike Taylor wrote: > On 4/26/23 9:36 AM, Mike Taylor wrote: > > > On 4/25/23 12:00 PM, Rick Byers wrote: > > > >> In terms of the standards / process piece, it looks as if the spec > >> PRs have all stalled for several months. What do you think is > >> necessary

Re: [blink-dev] Re: Intent to Ship: Local Network Access allowing same-origin fetches to potentially trustworthy origins

LGTM2 (sorry for the delay, it seems this fell out of our review queue). On 4/27/23 9:56 AM, Jonathan Hao wrote: Hi Yoav, It's been 2 weeks but no other API owners have replied.  Do you know if there's any blockers?  Should we ping the other API owners or could you help us? Best, Jonathan

Re: [blink-dev] Intent-to-Ship: MediaRecorder keyframe configurability

Great, with https://github.com/w3c/mediacapture-record/issues/219 filed and the discussion you linked to, I don't think this needs to block. LGTM1 to ship given a surface-level test in WPT as discussed. On Thu, Apr 27, 2023 at 1:40 PM Markus Handell wrote: > Yep this topic was discussed on >

Re: [blink-dev] Re: Intent to Ship: Local Network Access allowing same-origin fetches to potentially trustworthy origins

Hi Yoav, It's been 2 weeks but no other API owners have replied. Do you know if there's any blockers? Should we ping the other API owners or could you help us? Best, Jonathan On Wed, Apr 12, 2023 at 1:26 PM Yoav Weiss wrote: > LGTM1 > > Thanks for explaining! :) > > On Wed, Apr 12, 2023 at

Re: [blink-dev] Intent-to-Ship: MediaRecorder keyframe configurability

Yep this topic was discussed on https://github.com/w3c/mediacapture-record/pull/216#discussion_r1159521616 and earlier. In the end I backed out of my proposed semantics due to scepticism so the PR leaves it unspecified. During the interim that hbos@ speaks to where the PR was merged, it was

Re: [blink-dev] Intent-to-Ship: MediaRecorder keyframe configurability

On Thu, Apr 27, 2023 at 9:24 AM Markus Handell wrote: > >> Thanks for filing >> https://github.com/web-platform-tests/wpt/issues/39642, I've asked >> there for more details on what it would take to test this. >> >> > I added some more detail there. > > >> The spec change added two dictionary

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

LGTM3, thanks for measuring with use counter and aligning with Gecko and WebKit on this. On Wed, Apr 26, 2023 at 9:11 PM Mike Taylor wrote: > LGTM2 > On 4/26/23 11:28 AM, Mike West wrote: > > LGTM1. > > Testing looks good, and skipping the TAG review for features specified and > shipped in

Re: [blink-dev] Intent-to-Ship: MediaRecorder keyframe configurability

> > > Thanks for filing > https://github.com/web-platform-tests/wpt/issues/39642, I've asked > there for more details on what it would take to test this. > > I added some more detail there. > The spec change added two dictionary members to >

Re: [blink-dev] Intent to ship: VisibilityStateEntry

On Wed, 26 Apr 2023 at 18:53 Noam Rosenthal wrote: > > > On Wed, Apr 26, 2023 at 1:28 PM Yoav Weiss wrote: > >> Thanks for pushing this over the line!! >> >> On Tue, Apr 25, 2023 at 10:26 AM Noam Rosenthal >> wrote: >> >>> Contact emails...@chromium.org, nrosent...@chromium.org >>> >>>

Re: [blink-dev] Intent-to-Ship: MediaRecorder keyframe configurability

On Wed, Apr 26, 2023 at 5:36 PM Philip Jägenstedt wrote: > On Wed, Apr 26, 2023 at 12:42 PM Yoav Weiss > wrote: > >> >> >> On Fri, Apr 21, 2023 at 6:48 PM 'Markus Handell' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Contact emails: >>> >>> hande...@google.com >>> >>> Explainer: >>>

Re: [blink-dev] Intent to ship: VisibilityStateEntry

LGTM1 Please send a webkit position for this, even if it is non-blocking. On Wed, Apr 26, 2023 at 5:53 PM Noam Rosenthal wrote: > > > On Wed, Apr 26, 2023 at 1:28 PM Yoav Weiss wrote: > >> Thanks for pushing this over the line!! >> >> On Tue, Apr 25, 2023 at 10:26 AM Noam Rosenthal >>

Re: [blink-dev] Intent to Experiment: Dark mode support for web apps v2

M114 has recently branched which is the last milestone with this OT enabled. The feedback from the trial showed there was very little interest so we are just going to let it expire. Let me know if you want to chat further about this. On Thursday, November 24, 2022 at 10:43:13 AM UTC+11 Louise