- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Sep 2017 16:18:01 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Define serialization for background shorthand`, and agreed to the following resolutions: * `RESOLVED: postpone this until there's further evidence of use cases and move this to L4 if there is evidence` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Define serialization for background shorthand<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/418<br> <dael> fantasai: Defining serialization when splitting BG into multi long hands. Q is do we tackle in L3 or is L4 okay?<br> <dael> fantasai: Is it really important to converge now or are people happy to defer?<br> <dael> Rossen_: I'll piggyback on tantek point for use cases as well as ask if there are any impl that are currently seeing interop issues b/c of this and in any urgency to change their serialization.<br> <dael> Rossen_: I'm hearing silence which I am taking as no interest or use cases.<br> <dael> Rossen_: Obj to postponing this until there's further evidence of use cases and move this to L4 if there is evidence?<br> <tantek> +1 to at least postpone to L4, and note explicitly no use-cases<br> <florian> tantek: I agree, and even more so once we add the multiple borders we've resolved on, you even do explicit inset/outset at subpixel level on retina screens.<br> <dael> RESOLVED: postpone this until there's further evidence of use cases and move this to L4 if there is evidence<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/418#issuecomment-332575775 using your GitHub account
Received on Wednesday, 27 September 2017 16:17:51 UTC