- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2020 15:47:41 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Number of layers in getComputedStyle results`, and agreed to the following: * `RESOLVED: Have the computed value of the background / image layer properties match the number of items in the specified value` * `RESOLVED: Apply the rule for computed value list length of background properties to all other similar list repeating properties like masking, transitions, animations.` <details><summary>The full IRC log of that discussion</summary> <heycam> Topic: Number of layers in getComputedStyle results<br> <heycam> github: https://github.com/w3c/csswg-drafts/issues/4135<br> <heycam> fantasai: there's some inconsistency in how many layers we put in these properties<br> <heycam> ... the suggestion is to take the computed value's list length<br> <heycam> ... if you have a long list for background-image, but a short list for background-position<br> <heycam> ... when you return getCS, do you use the original list length, or the number of images?<br> <heycam> ... I think we should use the number of values specified<br> <heycam> oriol: in Chromium, this information is lost in the computed style<br> <heycam> ... inheriting onto children, the information is not inherited<br> <heycam> TabAtkins: this is a Chrome bug<br> <heycam> ... we should do the right thing and match Firefox here<br> <heycam> fantasai: let's do that, and clarify the Backgrounds spec<br> <heycam> ... which just says list, not how many items<br> <fantasai> file:///home/fantasai/w3c/csswg/css-backgrounds-3/Overview.html#background-repeat<br> <heycam> ... so clarify to the specified number of items<br> <fantasai> Computed value: list, each item a pair of keywords, one per dimension<br> <fantasai> list -> "list of the specified number of items"<br> <fantasai> or something<br> <fantasai> list (of the number of items specified)<br> <heycam> RESOLVED: Have the computed value of the background / image layer properties match the number of items in the specified value<br> <heycam> dbaron: other properties? transitions<br> <heycam> ... all of these cases are repeated lists where you key off one list to determine what happens<br> <fantasai> s/value/value of the property itself, not the reference property/<br> <heycam> ... but I think in all cases that is the right thing<br> <heycam> dbaron: transitions used to have two different types of list repeating<br> <heycam> TabAtkins: that's in V&U now<br> <fantasai> Not in Values. Values just as hhttps://drafts.csswg.org/css-values-4/#combining-values<br> <fantasai> https://drafts.csswg.org/web-animations-1/#animating-properties<br> <heycam> dbaron: backgrounds, masking, transitions, animations<br> <heycam> ... sounds like the relevant list here<br> <fantasai> ACTION: fantasai fix animation types of CSS Backgrounds<br> <heycam> RESOLVED: Apply the rule for computed value list length of background properties to all other similar list repeating properties like masking, transitions, animations.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4135#issuecomment-577249673 using your GitHub account
Received on Wednesday, 22 January 2020 15:47:43 UTC