- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 May 2017 17:01:51 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``Clarification about `Nx` as <resolution> value in image-set() is needed``, and agreed to the following resolutions: * `RESOLVED:` * `RESOLVED: add the x unit to <resolution> type in V&U` * `RESOLVED: revet the edit to image-set in CSS Images` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Clarification about `Nx` as <resolution> value in image-set() is needed<br> <dael> Github topic: https://github.com/w3c/csswg-drafts/issues/461<br> <Rossen_> I thought we had a resolution to *not* do this in Tokyo<br> <dael> astearns: Q if this is editorial or needs a resolution.<br> <dael> leaverou: In image set it allows values of 1x that is same as 1ppx. Even though the image had it it wasn't part of grammar. WE solved that by adding an x-resolution. So issue was addressed. It's grammar, not syntax.<br> <dael> leaverou: It's another question as to if it should be added, but that's V&U. As far as images is concerned grammar is on par with example.<br> <dael> fantasai: Do we want to add this to resolution type?<br> <dael> TabAtkins: I've been for that for a while.<br> <dael> leaverou: I'm not sure it's a good idea to take a single letter unit for a shortcut to another unit.<br> <dael> TabAtkins: We've done that. We won't use it elsewhere n ow.<br> <dael> leaverou: Then it is a better solution to add to the resolution section.<br> <dael> fantasai: We've never had alias units, so what do you get if you serialize it back out.<br> <dael> leaverou: dpx?<br> <leaverou> s/dpx/dppx/<br> <dael> TabAtkins: It's only image resolution and webkit image set, so let's see what webkit does and do what they say. It'll b e x or dppx.<br> <dael> smfr: Pretty sure it's x<br> <dael> fantasai: If you put in dppx do you get out x?<br> <dael> TabAtkins: In specified style no. We don't need fancy. They're different units with a 1 to 1 ratio. In computed when you canonicalize you go to probably x.<br> <dael> Florian_: What if you animate from one to the other?<br> <fantasai> https://www.w3.org/TR/css-values-3/#resolution<br> <dael> TabAtkins: over coputed values an all resolutions can be computed to each other<br> <dbaron> I'm trying to think about whether "x" makes sense for all uses of <resolution> or just some of them.<br> <dbaron> I think it's probably all.<br> <dael> astearns: Are we converging on using x everywhere <resolution> is possible?<br> <dael> TabAtkins: Let's leave that to testing. But do we add x to resolution and I'm a +1 to that.<br> <dael> astearns: Do we want tor esolve before we test?<br> <dael> TabAtkins: Is anyone going to obj based on the answer?<br> <dael> astearns: prop resolution is add the x unit to <resolution> type in V&U<br> <dael> leaverou: Yep.<br> <dael> astearns: Obj?<br> <dael> RESOLVED:<br> <dael> RESOLVED: add the x unit to <resolution> type in V&U<br> <dael> fantasai: L3 or L4?<br> <dael> astearns: I'd be happy for 4.<br> <dael> TabAtkins: It only has one impl.<br> <dael> astearns: Since it would go in 4 it means leave the edit in images in place b/c we don't want it to depend on L4 spec.<br> <dael> TabAtkins: Sure<br> <dael> fantasai: It's fine b/c you would have the impl that support L4...the testing would be part of L4 impl. It's like when we added q unit your lengths had more values possible.<br> <dael> astearns: Okay.<br> <dael> TabAtkins: Yeah, take it out of image set. It depends on resolution type.<br> <leaverou> agreed as well<br> <dael> astearns: Then we also need a resolution to revet the edit to image-set?<br> <dael> astearns: Obj?<br> <dael> RESOLVED: revet the edit to image-set in CSS Images<br> <dael> astearns: We're at time. Thanks everybody.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/461#issuecomment-298972588 using your GitHub account
Received on Wednesday, 3 May 2017 17:01:58 UTC