2023 a les 21:57:58 UTC+2, obr...@igalia.com
va escriure:
> Contact emails obr...@igalia.com
>
> Explainer
> https://www.smashingmagazine.com/2018/03/understanding-logical-properties-values/
>
> Specification https://drafts.csswg.org/css-logical/#directional-keywords
> https
I don't see the danger of a priority of constituencies inversion. Authors
can use preprocessors, just like they have been using for several years, so
I don't get where the hurry comes from.
In fact, I would argue that hurrying to ship a future without having
discussed the details just tends to r
st of work necessary to get this feature to a reasonable and pragmatic
>> state for shipping a v1.0 soon, on top of which we can continue iterating
>> together?
>>
>> Thanks,
>>Rick
>>
>>
>> On Fri, Jan 27, 2023 at 3:46 AM Philip Jägensted
solved? There are already 3 listed upthread, and I agree that
>>> anything that has a non-trivial risk of causing interop/compat problems
>>> down the line is worth spending extra time on.
>>>
>>> Best regards,
>>> Philip
>>>
>>> On Fri,
Will authors actually need to feature detect this? I mean, feature
detection won’t make a difference to visitors as it will have the same net
outcome to them: the nested styles will not be applied in browsers that
don’t support nesting.
I can imagine authors using nesting in inline styles, and
While https://wpt.fyi/css/css-pseudo/marker-font-variant-numeric-normal.html
uses nested ::marker, it's not the main point of the test.
In fact I was thinking of editing that test to allow it to pass on
implementations that do not support nested ::marker, but never got to do it.
So I think you sh
https://github.com/w3c/csswg-drafts/issues/4456 resolved to allow multiple
pseudo-elements in getComputedStyle.
I think it would be good to ship that ideally in the same release as this,
or at least not much later.
--
You received this message because you are subscribed to the Google Groups
"b
BTW, I remembered that I added a parsing test in the past:
https://wpt.fyi/results/css/css-pseudo/parsing/tree-abiding-pseudo-elements.html
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails fr
> I'm inclined to get things into the world
I'm inclined to not hurry to get things into the world, specially since you
warned the CSSWG that you may block refinements after shipping (
https://groups.google.com/a/chromium.org/g/blink-dev/c/GISQbW0Xhxg/m/h4rarOM2BgAJ
).
But well, let's see how Da
The last 3 tests are for grid-template-rows, which requires also display:
grid, and some elements inside the grid, but the person who added the test
didn't change HTML, so the test is wrongly expects a value, but in always
will be 'none'.
You don't need `display: grid` in order to compute `g
I think it would be good to wait for the CSSWG to clarify things like
https://github.com/w3c/csswg-drafts/issues/11784 before shipping.
El dia dissabte, 8 de març del 2025 a les 2:59:22 UTC+1, David Grogan va
escriure:
> Contact emailsdgr...@chromium.org
>
> ExplainerBehaves as 100%, except it
11 matches
Mail list logo
