Although I think `view-transition-name: auto` is a mistake, I support
`match-element` landing.
I don't think web developers as a whole have a good understanding of DOM
node equality, and as folks use it outside of small demos they'll likely be
caught out by nodes being unexpectedly unequal, due
Safari 18.4 has released `text-autospace`[1], and the Chinese community has
responded enthusiastically.
What's the status in Chrome now? We're really looking forward to shipping
in Chrome.
[1]:
https://webkit.org/blog/16574/webkit-features-in-safari-18-4/#:~:text=with%20support.-,Text%20auto%2
Have you proposed that a standards body adopt this into a working group of
some sort? Especially since Safari is doing something similar, it seems
like the WHATWG might be willing to adopt this into the Fetch standard.
I'm also somewhat concerned about the internationalization concerns
expressed i
Can I get an update on this?
Thanks,
--Benjamin "Russ" Hamilton
On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor wrote:
> LGTM2
> On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote:
>
> Yes, it's just a performance/ergonomics change. Developers could
> previously get the same effect by callin
LGTM3
On Tuesday, April 1, 2025 at 3:51:41 PM UTC-4 beham...@google.com wrote:
> Can I get an update on this?
>
> Thanks,
> --Benjamin "Russ" Hamilton
>
> On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor
> wrote:
>
>> LGTM2
>> On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote:
>>
>> Yes, it'
LGTM1
On Wednesday, March 26, 2025 at 5:38:45 PM UTC-4 Di Zhang wrote:
> The WPT tests failing is mostly because Safari still using the old
> specification for getComposedRanges() syntax. This change was resolved in
> September 2024: https://github.com/w3c/selection-api/pull/331
>
> I have open
Some cameras and media will immediately begin exposing orientation
information. In uncommon cases this orientation may change. If orientation
changes during encoding through VideoEncoder frames with different
orientation than the first are currently encoded with incorrect size and
orientation
On 4/1/25 5:00 PM, Jeffrey Yasskin wrote:
Have you proposed that a standards body adopt this into a working
group of some sort? Especially since Safari is doing something
similar, it seems like the WHATWG might be willing to adopt this into
the Fetch standard.
I think it may be possible to sta
Note that we've agreed to separate this intent into two separate intents
for `match-element`
(https://groups.google.com/a/chromium.org/g/blink-dev/c/o3JcMI6dGdY/m/bg3z-WX3BwAJ)
and `auto`
(https://groups.google.com/a/chromium.org/g/blink-dev/c/KCizytrJUMA/m/dqg_mEX4BwAJ).
This intent is depr
Can you file the various review gates as well?
[image: Screenshot 2025-04-01 at 10.42.12 PM.png]
TAG reviewTo be filed
Is this accurate?
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails
LGTM1
Interoperability risk is relatively low. The main risk is that other
browsers do not implement the feature. However, since the feature is a
small addition to an existing spec and it has consensus across browsers, it
is possible that it will be implemented. There is no compatibility risk
On Tue, Apr 1, 2025 at 7:16 PM Vladimir Levin wrote:
> Some cameras and media will immediately begin exposing orientation
> information. In uncommon cases this orientation may change. If orientation
> changes during encoding through VideoEncoder frames with different
> orientation than the first
This does not change the privacy story nor does it introduce a privacy
regression, as cross-origin subframes can currently postMessage() data to
the root that the root frame can then use as automatic beacon data. Both
the existing capability as well as the proposed changes involve the root
fe
Contact emails
victor...@chromium.org, miketa...@chromium.org
Explainer
https://github.com/explainers-by-googlers/reduce-accept-language
TAG reviewTo be filedSummary
In order to reduce the amount of passively available entropy in HTTP
requests, we want to reduce the amount of information the A
LGTM1
On Tue, Apr 1, 2025 at 5:25 AM Domenic Denicola
wrote:
> Contact emailsrobert...@chromium.org, dome...@chromium.org
>
> Explainer
> https://github.com/WICG/nav-speculation/blob/main/speculation-rules-tags.md
>
> Specificationhttps://wicg.github.io/nav-speculation/speculation-rules.html
>
15 matches
Mail list logo
