Re: [blink-dev] Intent to Ship: Independent/Individual Properties for CSS Transforms

ego Casasnovas > wrote: > >> LGTM3. >> >> On 21/10/2021 19:53, Daniel Bratell wrote: >> > LGTM2. >> > >> > /Daniel >> > >> > On 2021-10-21 08:19, Yoav Weiss wrote: >> >> LGTM1 >>

[blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

Contact emailsdba...@chromium.org ExplainerNone Specificationhttps://www.w3.org/TR/css-values-3/#custom-idents Summary The CSS keyword 'default' is not allowed within CSS custom identifiers, which are used for many types of user-defined names in CSS (for example, names created by @keyframes rul

Re: [blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

ithub.com/webcompat/web-bugs/issues?q=is%3Aissue+elster> a bunch of webcompat issues with Firefox, but none of the ones in that list seem related to this issue. -David On Thu, Jul 7, 2022 at 1:00 AM Yoav Weiss wrote: > > > On Wed, Jul 6, 2022 at 9:50 PM David Baron wrote:

Re: [blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

On Thu, Jul 7, 2022 at 10:36 AM David Baron wrote: > Most relevant to this intent is the case on http://www.elster.de where > default is used (which is the only actual site that I'm aware of this > change affecting): it is a use in the animation-name property. The > relevan

Re: [blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

On Mon, Jul 11, 2022 at 12:10 PM Joe Medley wrote: > In which milestone will this be removed? > Assuming nothing changes, Chrome 105. I've updated chromestatus. On Thu, Jul 7, 2022 at 10:36 AM David Baron wrote: > As far as what the breakage might look like: it would look

[blink-dev] Intent to Implement and Ship: transform: perspective(none)

Contact emailsdba...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-transforms-2/#funcdef-perspective Summary Implement support for a 'none' argument to the perspective() function within the syntax of the CSS transform property. This provides the perspective() function wit

Re: [blink-dev] Intent to Implement and Ship: transform: perspective(none)

eed it looks like this is already passing in Firefox: > > https://wpt.fyi/results/css/css-transforms/animation/transform-interpolation-001.html?label=experimental&label=master&aligned > > On Thu, Oct 7, 2021 at 8:49 AM Manuel Rego Casasnovas > wrote: > >>

[blink-dev] Intent to Ship: Independent/Individual Properties for CSS Transforms

Contact emailsdba...@chromium.org, kev...@chromium.org, fla...@chromium.org ExplainerNone Specification https://drafts.csswg.org/css-transforms-2/#individual-transforms Summary This adds three new CSS properties: translate, rotate, and scale. This exposes a simple way for web developers to acce

Re: [blink-dev] Intent to Ship: HDR CSS Media Queries

The spec requires that "The combination of the User Agent and the output device fulfill all of the following criteria" when describing what it means to be high dynamic-range. Since Chromium doesn't support wide-gamut colors in CSS, HTML, or Can

Re: [blink-dev] Intent to Ship: HDR CSS Media Queries

This sounds like exactly the sort of case where an implementation should report (dynamic-range: standard) and (video-dynamic-range: high). It would be great to see the spec clarified to make it clearer what UA support is expected for each, though. -David On Thu, Oct 21, 2021 at 7:03 PM Will Cass

Re: [blink-dev] Intent to Ship: HDR CSS Media Queries

ink it's potentially okay to ignore those definitions, but I'd ask >> for a rationale here. >> >> I think it's a great thing to summarize hdr into a single media query, >> but the risk here would be to release a semantic that guarantees very >> little, and the

[blink-dev] Intent to Prototype: CSS toggles

Contact emailsdba...@chromium.org, ns...@google.com Explainerhttps://css.oddbird.net/toggles/explainer/ Specificationhttps://tabatkins.github.io/css-toggle/ Summary CSS toggles are a mechanism for associating toggleable state with a DOM element. This state can be defined and connected to activa

Re: [blink-dev] Intent to Prototype: CSS toggles

On Tue, Apr 19, 2022 at 10:32 AM Mike Taylor wrote: > Specification https://tabatkins.github.io/css-toggle/ > > A question came up in Security & Privacy review today. Can you clarify > what "persistent state" means in > https://tabatkins.github.io/css-toggle/#toggles? I suspect we're not > re-inv

[blink-dev] Re: RuntimeEnabledFeatures flags that we might be able to remove

he previous version of the sheet in the second tab.) As before, hopefully this will prompt some removal of flags that we don't need any longer. -David On Fri, Jan 12, 2024 at 11:39 AM David Baron wrote: > Since we've recently been more careful about creating feature flags for > change

[blink-dev] Intent to Ship: CSS interpolate-size property and calc-size() function

Contact emailsdba...@chromium.org Explainer https://github.com/w3c/csswg-drafts/blob/main/css-values-5/calc-size-explainer.md Specificationhttps://drafts.csswg.org/css-values-5/#calc-size Summary The CSS interpolate-size property allows a page to opt in to animations and transitions of CSS intr

Re: [blink-dev] Intent to Ship: CSS interpolate-size property and calc-size() function

I suppose mostly the test naming as "tentative" just needs to be updated, but I was planning to do it along with landing the one line changes to the property value definitions (which I mentioned in the "Anticipated spec changes" section of the intent), since technically it's testing stuff that isn'

Re: [blink-dev] Intent to Ship: CSS interpolate-size property and calc-size() function

om/web-platform-tests/wpt/pull/47297>). -David On Mon, Jul 22, 2024 at 8:19 PM Domenic Denicola wrote: > > > On Tue, Jul 16, 2024 at 12:23 AM David Baron wrote: > >> Contact emailsdba...@chromium.org >> >> Explainer >> https://github.com/w3c/cssw

[blink-dev] Re: RuntimeEnabledFeatures flags that we might be able to remove

update. As before, please have a look to see if there are feature flags that you can remove because they're no longer needed. -David On Thu, Mar 21, 2024 at 8:51 PM David Baron wrote: > I've updated the spreadsheet of stable feature flags > <https://docs.

[blink-dev] Intent to Ship: allow more pseudo-elements and pseudo-classes after ::part()

Contact emailsdba...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-shadow-parts-1/#part Summary CSS selectors that use the ::part() pseudo-element are allowed to have other CSS pseudo-elements (except ::part()) and many types of other CSS pseudo-classes after them. (Combi

[blink-dev] Intent to Ship: Accordion pattern using name attribute on elements

Contact emailsdba...@chromium.org Explainerhttps://open-ui.org/components/accordion.explainer Specificationhttps://github.com/whatwg/html/pull/9400 Summary This feature adds the ability to construct exclusive accordions using a sequence of HTML elements. It adds a name attribute to the elemen

[blink-dev] Intent to Ship: CSS :dir() pseudo-class selector

Contact emailsdba...@chromium.org, dizha...@chromium.org, myid.s...@igalia.com ExplainerNone Specificationhttps://www.w3.org/TR/selectors-4/#the-dir-pseudo Summary The :dir() CSS pseudo-class selector matches elements based on directionality, which is determined based on the HTML dir attribute.

Re: [blink-dev] Intent to Ship: Accordion pattern using name attribute on elements

On Wed, Oct 4, 2023 at 6:30 AM Yoav Weiss wrote: > > On Fri, Sep 29, 2023 at 11:04 PM David Baron wrote: > >> Summary >> >> This feature adds the ability to construct exclusive accordions using a >> sequence of HTML elements. It adds a name attribute to the &g

[blink-dev] Intent to Prototype: CSS calc-size() function

Contact emailsdba...@chromium.org ExplainerNone yet. (But the starting point for writing one, particularly a section on alternatives considered, would probably be the discussion in the github issue starting from Tab's November 6 comment

Re: [blink-dev] Intent to implement and ship: Allow elements with CSS display:contents to be focusable

be to accumulate the rectangles of all children and to >> use that. Not sure what the algorithm would do for out-of-flow children. >> >> Aaron >> >> On Tue, Jan 9, 2024 at 11:39 AM David Baron wrote: >> >>> Contact emailsdba...@chromium.org >>>

Re: [blink-dev] Intent to implement and ship: Allow elements with CSS display:contents to be focusable

discourage having to go down that path). -David On Tue, Jan 9, 2024 at 12:49 PM Aaron Leventhal wrote: > Would an option for focus outlines to be to use the same idea we're > discussing for AT bounding boxes? Namely, to use an aggregation of child > outlines? > > On Tue, Jan 9

Re: [blink-dev] Intent to implement and ship: Allow elements with CSS display:contents to be focusable

Jan 9, 2024 at 2:56 PM David Baron wrote: > >> I think in theory it might make sense for focus outlines to use something >> like an aggregation of child bounds. (The specifications even allow focus >> outlines on regular elements to expand to contain the bounds of ch

[blink-dev] Re: Intent to implement and ship: Allow elements with CSS display:contents to be focusable

On Wed, Jan 10, 2024 at 11:14 AM Yoav Weiss wrote: > > > On Tuesday, January 9, 2024 at 5:39:19 PM UTC+1 David Baron wrote: > > Contact emailsdba...@chromium.org > > ExplainerNone > > Specificationhttps://github.com/w3c/csswg-drafts/issues/2632# > issuecomment-43

[blink-dev] RuntimeEnabledFeatures flags that we might be able to remove

Since we've recently been more careful about creating feature flags for changes that have the possibility of breaking content, we've also been creating more feature flags than before. This means that we're also creating a larger number of feature flags that have shipped to stable, been shown to be

Re: [blink-dev] Re: Intent to Prototype: document.caretPositionFromPoint API

For what it's worth, some of the historical context around the 2009 changes is in WebApps TPAC 2009 minutes and Anne's folllowup email to www-style . -David On Tue, Jan 23

Re: [blink-dev] Intent to Prototype: CSS headline balancing (`text-wrap: balance`)

On Tue, Feb 7, 2023 at 7:31 AM Koji Ishii wrote: > Specification > https://w3c.github.io/csswg-drafts/css-text-4/#valdef-text-wrap-balance > > Summary > > Enables the lengths of lines in a paragraph balanced, for better > readability and to prevent typographic widows. This feature is often used >

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

A few notes on the history of this feature that relate to some of the questions asked: When font-variant-position was being designed, the CSS Working Group had an extensive discussion (part 1 , part

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

On Fri, Feb 24, 2023 at 5:49 AM Yoav Weiss wrote: > On Fri, Feb 24, 2023 at 11:27 AM Manuel Rego Casasnovas > wrote: > >> There's a CSSWG issue about this topic in particular: >> https://github.com/w3c/csswg-drafts/issues/7441 > > > Is this something that can be put on the agenda for the CSSWG t

Re: [blink-dev] Intent to Prototype: CSS inline leading-trim

Does this also involve implementing the text-edge property (which leading-trim depends on)? It also seems like it may be worth starting a discussion in the CSS Working Group about implementation status, given that the spec says "Do not implement (yet)". I also think the summary of the issues WebK

Re: [blink-dev] Intent to Prototype: CSS font-size-adjust: two-value syntax

On Mon, Mar 27, 2023 at 6:33 PM ChangSeok Oh wrote: > * Interoperability and Compatibility* > >Gecko: Publicly support > >WebKit: Positive and in development >https://bugs.webkit.org/show_bug.cgi?id=254191 >https://github.com/WebKit/WebKit/pull/11744 (I am the author) >

[blink-dev] Intent to Prototype: Accordion pattern using elements

Contact emailsdba...@chromium.org Explainerhttps://open-ui.org/components/accordion.explainer https://github.com/dbaron/details-styling SpecificationNone Summary This is a set of work to enable better platform support for the accordion widget

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

pecific outreach, and possibly even interventions of some form (like > using a fallback font?). > > Rick > > On Fri, Feb 24, 2023 at 9:22 AM David Baron wrote: > >> On Fri, Feb 24, 2023 at 5:49 AM Yoav Weiss >> wrote: >> >>> On Fri, Feb 24, 2023 at 11:27 A

Re: [blink-dev] Intent to Ship: CSS font-variant-position property

to a >> non-trivial problem in practice. >> >> If we were to ship without synthesis, would it be practical to have a >> UseCounter which measures how often we see font-variant-position used with >> a font that lacks the glyphs? This would tell us how important th

[blink-dev] Re: Intent to Ship: allow more pseudo-elements and pseudo-classes after ::part()

On Tue, Sep 3, 2024 at 11:00 PM Domenic Denicola wrote: > > On Thursday, August 29, 2024 at 12:48:36 AM UTC+9 David Baron wrote: > > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues