On Wednesday, May 21, 2025 at 10:31:06 PM UTC+9 Mike Taylor wrote:
On 5/20/25 6:06 AM, Chromestatus wrote:
Contact emails robert...@chromium.org
Explainer https://github.com/WICG/nav-speculation/blob/main/
triggers.md#window-name-targeting-hints
Specification https://wicg.github.io/nav-spec
Wouldn't the answer be to make the viewport units behave like container
query units?
It feels like container queries hit all these problems and came up with
solutions. There may be additional issues, but it seems like a better
starting point.
On Thu, 22 May 2025, 18:17 Chris Harrelson, wrote:
>
I've skimmed through these docs, and personally it seems like an
unnecessary feature.
The explainer says a considered alternative is
"font-size: medium would always be affected by the OS-level font scale."
with cons
"Sites are NOT built correctly and things that used to just look small
would now b
On Fri, May 23, 2025 at 9:00 AM Chromestatus <
ad...@cr-status.appspotmail.com> wrote:
> Contact emails dgro...@chromium.org, p...@chromium.org
>
> Explainer https://davidsgrogan.github.io/env-explainer.html
>
> Specification https://drafts.csswg.org/css-env-1/#text-zoom
>
> Summary
>
> Exposes a
Contact emails
dgro...@chromium.org, p...@chromium.org
Explainer
https://davidsgrogan.github.io/env-explainer.html
Specification
https://drafts.csswg.org/css-env-1/#text-zoom
Summary
Exposes a user's preferred font scale to CSS. Currently, it is not practical
for a page to detect if the use
Contact emails
lu...@microsoft.com, luigo...@microsoft.com, dmu...@chromium.org
Explainer
https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md
Specification
https://github.com/WICG/manifest-incubations/pull/113
Design docs
https://docs.google.com/document/
Hi Tom,
Bit late to the party, but I wanted to mention that even in the transition
to PQC, Ed25519 is still relevant, in hybrid/composite constructions; the
idea being that you sign and verify with both algorithms, so that an
attacker would need to break both of them.
For example, see draft-iet
Contact emails
alcoo...@chromium.org
Explainer
https://github.com/immersive-web/depth-sensing/blob/main/explainer.md
Specification
https://immersive-web.github.io/depth-sensing
Design docs
https://docs.google.com/document/d/1Nx3hCHqq8UZ6E1nxctmkr6BBQKwf3AgIai7WVsQ_nUM/edit?usp=sharing
Summ
On Tue, May 20, 2025 at 12:05 AM Jake Archibald
wrote:
> I think the "one shot" nature of this means it misses a lot of use-cases,
> such as the Discus case given in the explainer. Could the size be updated
> continually with the same constraints applied to CSS containers? This would
> also allow
LGTM3
(Not all chromestatus reviews have completed so pay attention to
additional feedback there; though I don't expect any or I would not have
sent the LGTM)
/Daniel
On 2025-05-22 15:19, Yoav Weiss (@Shopify) wrote:
LGTM2
This is an exciting feature that will enable the adoption of more
LGTM2
This is an exciting feature that will enable the adoption of more
aggressive speculation rules in scenarios that are too risky to deploy
today!
On Thu, May 22, 2025 at 2:10 PM Mike Taylor wrote:
> On 5/22/25 1:16 AM, Domenic Denicola wrote:
>
> On Wed, May 21, 2025 at 9:48 PM Mike Taylor
On 5/22/25 1:16 AM, Domenic Denicola wrote:
On Wed, May 21, 2025 at 9:48 PM Mike Taylor
wrote:
On 5/20/25 10:07 PM, Domenic Denicola wrote:
(Feature-collaborator hat on, API owners hat off.)
Thanks for sending this! A few minor corrections here, that it'd
be good to make to
12 matches
Mail list logo
