[blink-dev] Intent to Ship: Short-circuiting var(), attr()

Contact emails andr...@chromium.org Explainer When designing the if() function, we (CSSWG) decided to make it short-circuiting , such that we can stop evaluation once a matching condition is fo

[blink-dev] Re: Intent to Ship: CSS Custom Functions (@function)

See updates inline: On Wed, Feb 26, 2025 at 10:10 PM Anders Hartvoll Ruud wrote: > Note that this was targeting the M136 release, so we would have had > another month to tweak this feature, and even a couple of weeks after that > to land finishing touches (or to disable the feature, w

Re: [blink-dev] Intent to Ship: Type-agnostic var() fallback

> LGTM1 contingent on that. > > Best, > > Alex > > On Tuesday, March 11, 2025 at 3:20:38 AM UTC-7 Anders Hartvoll Ruud wrote: > >> On Mon, Mar 10, 2025 at 8:37 PM Mike Taylor >> wrote: >> >>> Could you please request the privacy, security, enterpr

Re: [blink-dev] Intent to Ship: Type-agnostic var() fallback

On Mon, Mar 10, 2025 at 8:37 PM Mike Taylor wrote: > Could you please request the privacy, security, enterprise, etc bits in > your chromestatus entry? > Ah, yes. Done. On 3/7/25 7:31 AM, Anders Hartvoll Ruud wrote: > > Contact emails > > andr...@chromium.org > > Exp

[blink-dev] Intent to Ship: Type-agnostic var() fallback

Contact emails andr...@chromium.org Explainer A var() function can provide a fallback value, in case the referenced custom property does not exist (or is invalid in some other way): .component { width: var(--component-width, 100px); } When custom properties are registered

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Interpolation progress functional notations: CSS *progress() functions

Note that we are discussing dropping media-progress() and container-progress() from the spec. https://github.com/w3c/csswg-drafts/issues/11826 We should probably keep those variants behind a flag until the issue is resolved. On Thu, Feb 27, 2025 at 5:08 PM 'Daniil Sakhapov' via blink-dev < blink-

[blink-dev] Re: Intent to Ship: CSS Custom Functions (@function)

Note that this was targeting the M136 release, so we would have had another month to tweak this feature, and even a couple of weeks after that to land finishing touches (or to disable the feature, worst case). As for signals, concerns could have been raised at any time between December 18th and no

[blink-dev] Re: Intent to Ship: CSS Custom Functions (@function)

+Tab Atkins On Tue, Feb 25, 2025 at 9:06 PM Alan Stearns wrote: > This is a feature that is greatly desired by developers, and as such runs > increased risk that whatever gets shipped first gets heavily used and then > cannot be improved due to web compat. I think it’s premature to ship > witho

[blink-dev] Intent to Ship: CSS Custom Functions (@function)

Contact emails andr...@chromium.org, se...@chromium.org Explainer https://css.oddbird.net/sasslike/mixins-functions Note: the explainer includes a description of mixins as well. This intent covers custom functions (@function) only. Specification https://drafts.csswg.org/css-mixins-1 Note: de

Re: [blink-dev] Intent to Ship: The Nested Declarations Rule

On Fri, Aug 2, 2024 at 11:06 AM Anders Hartvoll Ruud wrote: > On Fri, Aug 2, 2024 at 1:54 AM Daniel Clark wrote: > >> The stated answer to “Will this feature be supported on all six Blink >> platforms” is “No”, but I’d expect this to be the same on all platforms – >> i

Re: [blink-dev] Intent to Ship: The Nested Declarations Rule

>>>> LGTM1, this is important to do sooner rather than later, so that the >>>> current behavior is not locked in by site compat. Thank you for finding a >>>> solution that's acceptable to everyone! >>>> >>>> Given that this was discu

Re: [blink-dev] Intent to Ship: The Nested Declarations Rule

d as if this will have a flag. I'll post the flag name to this thread before shipping. > -- Dan > > > > *From:* Anders Hartvoll Ruud > *Sent:* Thursday, August 1, 2024 4:14 AM > *To:* blink-dev > *Subject:* [blink-dev] Intent to Ship: The Nested Declarati

[blink-dev] Intent to Ship: The Nested Declarations Rule

Note: See also the previous (failed) intent for @nest. All CSSWG disagreements around this are now resolved. Contact emails andr...@chromium.org Specification https://drafts.csswg.org/css-nesting-1/#nested-declarations-rule S

[blink-dev] Re: Intent to Ship: CSS Anchor Positioning: Unwrapped inset-area()

On Wed, Jul 3, 2024 at 11:35 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Wednesday, July 3, 2024 at 10:47:21 AM UTC+2 Anders Hartvoll Ruud wrote: > > Contact emailsandr...@chromium.org > > ExplainerNone > > Specificationhttps://draft

Re: [blink-dev] Re: Web-Facing Change PSA: Rename position-try-options to position-try-fallbacks

I'll answer since Mason is now OOO. On Tue, Jul 2, 2024 at 8:48 AM Yoav Weiss (@Shopify) wrote: > > > On Tuesday, July 2, 2024 at 12:38:50 AM UTC+2 Mason Freed wrote: > > Contact emailsmas...@chromium.org, andr...@chromium.org > > Specificationhttps://github.com/w3c/csswg-drafts/issues/10395# >

[blink-dev] Intent to Ship: CSS Anchor Positioning: Unwrapped inset-area()

Contact emailsandr...@chromium.org ExplainerNone Specification https://drafts.csswg.org/css-anchor-position-1/#position-try-fallbacks Summary Replaces the inset-area() function with inset-area values directly within position-try-fallbacks. This means that you now just write e.g. position-try-fa

Re: [blink-dev] Intent to Ship: Stable Bare Declarations (@nest)

Oops, I intended to send that e-mail to the list, must have hit "Reply" instead of "Reply All". On Fri, Apr 26, 2024 at 10:45 AM Anders Hartvoll Ruud wrote: > > > On Fri, Apr 26, 2024 at 4:09 AM Domenic Denicola > wrote: > >> >> >> On Thu, A

[blink-dev] Intent to Ship: Stable Bare Declarations (@nest)

Contact emails andr...@chromium.org Specification https://drafts.csswg.org/css-nesting-1/#nest-rule Summary CSS Nesting initially shipped with an interesting quirk that would cause bare declarations that come after a nested rule to “shift”, for example: .foo { width: 100px; height: 100p

Re: [blink-dev] Intent to Ship: CSS Highlight Inheritance

On Tue, Oct 31, 2023 at 1:45 PM Stephen Chenney wrote: > Contact emailsschen...@chromium.org > > Specificationhttps://drafts.csswg.org/css-pseudo-4/#highlight-cascade > > Summary > > With CSS Highlight Inheritance, the CSS Highlight pseudo classes, such as > ::selection and ::highlight, inherit t

[blink-dev] Re: Intent to Ship: Relaxed CSS Nesting

On Mon, Oct 2, 2023 at 1:29 PM Anders Hartvoll Ruud wrote: > Contact emails > > andr...@chromium.org > > Specification > > https://drafts.csswg.org/css-syntax/#consume-block-contents > > Summary > > Allows nested style rules > <https://drafts.csswg.org/css

Re: [blink-dev] Intent to Ship: Relaxed CSS Nesting

On Tue, Oct 3, 2023 at 8:46 PM Anders Hartvoll Ruud wrote: > On Tue, Oct 3, 2023 at 3:14 PM Yoav Weiss wrote: > >> LGTM1 >> >> Thanks for evaluating the compat risk for this. While non-zero, it seems >> manageable given Mozilla already shipping this, with Safari

Re: [blink-dev] Intent to Ship: Relaxed CSS Nesting

anging from one kind of invalid/has-no-effect to a *slightly* different kind of invalid/has-no-effect. > On Mon, Oct 2, 2023 at 1:30 PM Anders Hartvoll Ruud > wrote: > >> Contact emails >> >> andr...@chromium.org >> >> Specification >> >> http

[blink-dev] Intent to Ship: Relaxed CSS Nesting

Contact emails andr...@chromium.org Specification https://drafts.csswg.org/css-syntax/#consume-block-contents Summary Allows nested style rules to begin with an identifier. For example, the following will now be possible: p { span

Re: [blink-dev] Intent to Ship: view-timeline shorthand sets view-timeline-inset

On Wed, Aug 23, 2023 at 3:23 PM Yoav Weiss wrote: > > > On Wed, Aug 23, 2023 at 2:46 PM Anders Hartvoll Ruud > wrote: > >> Contact emails >> >> >> *andr...@chromium.org *Specification >> >> >> *https://github.com/w3c/csswg-drafts/issues

[blink-dev] Intent to Ship: view-timeline shorthand sets view-timeline-inset

Contact emails *andr...@chromium.org *Specification *https://github.com/w3c/csswg-drafts/issues/8926 *Summary *The view-timeline shorthand is now a shorthand for view-timeline-name, view-timeline-axis, and view-timeline-inset. Previo

Re: [blink-dev] Intent to Ship: @scope

On Wed, Jun 7, 2023 at 5:54 PM slightlyoff via Chromestatus < admin+slightly...@cr-status.appspotmail.com> wrote: > LGTM3. If we have a potential `:visited` issue, we should make sure this > is shipped with a feature flag for the next few releases. The long term > solution for `:visited` is to mak

Re: [blink-dev] Intent to Ship: @scope

ote: >>> >>> LGTM1 >>> >>> This seems like an obvious useful addition with relatively broad >>> consensus around it. Thanks for working on this! >>> >>> On Thu, Jun 1, 2023 at 10:39 AM Anders Hartvoll Ruud < >>> an

[blink-dev] Intent to Ship: @scope

Contact emails andr...@chromium.org Explainer https://css.oddbird.net/scope/explainer Specification https://drafts.csswg.org/css-cascade-6/#scope-atrule Summary Allows authors to scope style rules to a given element. The key differences between this and regular descendant combinators are:

Re: [blink-dev] Intent to Ship: CSS Nesting

PSA: CSS Nesting Still Shipping in M112 I've been experimenting with parser restarts in Blink lately, which would allow nested selectors that start with tag names. I've shared my results with the CSSWG (Issue 7961, comment ).

Re: [blink-dev] Intent to Remove: -webkit-perspective-origin-[x,y]

On Fri, Oct 28, 2022 at 2:04 AM Mike Taylor wrote: > On 10/27/22 5:41 AM, Anders Hartvoll Ruud wrote: > > On Thu, Oct 27, 2022 at 11:27 AM Manuel Rego Casasnovas > wrote: > >> What's the status in other browsers? >> > >- WebKit does not support it (any

Re: [blink-dev] Intent to Remove: -webkit-perspective-origin-[x,y]

On Thu, Oct 27, 2022 at 11:27 AM Manuel Rego Casasnovas wrote: > > On 27/10/2022 11:11, Anders Hartvoll Ruud wrote: > > Gecko: No signal > > > > > > WebKit: No signal > > What's the status in other browsers? > > - Gecko does not s

[blink-dev] Intent to Remove: -webkit-perspective-origin-[x,y]

Contact emails *andr...@chromium.org *Explainer *None*Specification *N/A*Summary *Removes the non-standard -webkit-perspective-origin-[x,y] CSS properties. Note however that the -webkit-perspective-origin property (an alias of perspective-origin) is not affected.The regular (parsing-based

[blink-dev] Intent to Ship: CSS Values and Units Module Level 4: Small/Large/Dynamic/Logical viewport units

Contact emails andr...@chromium.org Explainer https://github.com/w3ctag/design-reviews/issues/706#issuecomment-108242 https://www.bram.us/2021/07/08/the-large-small-and-dynamic-viewports/ Specification https://drafts.csswg.org/css-values-4/#viewport-relative-lengths Summary Support for

[blink-dev] Intent to Ship: Container Queries

Contact emails andr...@chromium.org, futh...@chromium.org Explainer https://css.oddbird.net/rwd/query/explainer/ Specification https://drafts.csswg.org/css-contain-3/#container-queries Scope This intent covers: - Size queries

Re: [blink-dev] Intent to Ship: Media Queries Level 4 Syntax & Evaluation

articular release. But if you want a prediction anyway, then likely >> 104. >> >> >>> >>> On Monday, April 11, 2022 at 7:17:45 AM UTC-7 Emilio Cobos Alvarez wrote: >>> >>>> >>>> >>>> On 4/11/22 15:02, Anders Hartvoll Ruud

[blink-dev] Re: Intent to Ship: Media Queries Level 4 Syntax & Evaluation

On Mon, Apr 11, 2022 at 1:40 PM Anders Hartvoll Ruud wrote: > Contact emails > > > *andr...@chromium.org kbabb...@microsoft.com > *Explainer > > > > *NoneThis article by Bramus > <https://www.bram.us/2021/10/26/media-queries-level-4-media-query-range-contexts/

Re: [blink-dev] Intent to Ship: Media Queries Level 4 Syntax & Evaluation

AM UTC-7 Emilio Cobos Alvarez wrote: > >> >> >> On 4/11/22 15:02, Anders Hartvoll Ruud wrote: >> > Ah, I'm not familiar with that way of doing compat research. What would >> > we gain from doing that vs. regular use-counter + HTTP Archive? >> &

Re: [blink-dev] Intent to Ship: Media Queries Level 4 Syntax & Evaluation

On Mon, Apr 11, 2022 at 1:57 PM Yoav Weiss wrote: > Thanks for working on this!! > > On Mon, Apr 11, 2022 at 1:41 PM Anders Hartvoll Ruud > wrote: > >> Contact emails >> >> >> *andr...@chromium.org kbabb...@microsoft.com >> *Explainer >

[blink-dev] Intent to Ship: Media Queries Level 4 Syntax & Evaluation

Contact emails *andr...@chromium.org kbabb...@microsoft.com *Explainer *NoneThis article by Bramus may be helpful.*Specification *https://www.w3.org/TR/mediaqueries-4/#mq-range-context

[blink-dev] Intent to Prototype: @scope

Contact emailsandr...@chromium.org Explainerhttps://css.oddbird.net/scope/explainer/ Specificationhttps://drafts.csswg.org/css-cascade-6/#scope-atrule Summary Allows authors to scope style rules to a given element. The key difference between this and a regular descendant combinator is that the

Re: [blink-dev] Intent to Ship: hwb() color notation

gt; > Joe > Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | > 816-678-7195 > *If an API's not documented it doesn't exist.* > > > On Tue, Feb 8, 2022 at 2:41 AM Anders Hartvoll Ruud > wrote: > >> Contact emailsandr...@chromium.org, o

[blink-dev] Intent to Ship: hwb() color notation

Contact emailsandr...@chromium.org, on behalf of: jan.kei...@gmail.com ExplainerNone Specificationhttps://drafts.csswg.org/css-color/#the-hwb-notation Summary HWB (short for Hue-Whiteness-Blackness) is another method of specifying sRGB colors, similar to HSL, but often even easier for humans