[Webkit-unassigned] [Bug 99725] image-set doesn't round-trip properly with cssText

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=99725





--- Comment #4 from Rick Byers <rbyers at chromium.org>  2012-10-19 08:56:03 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > FYI, neither CSS OM or DOM-2 Style specifies (at present) what cssText (of a specified style, i.e., elt.style) should be if the declaration encounters a parse error. In fact, whether a rule should be instantiated in the OM in this case is similarly unspecified. So any WK behavior in this regard should be considered experimental and WK specific (at least as far as the specs are currently written).
> > 
> > Makes sense.  But I'm talking only about valid CSS here (per http://dev.w3.org/csswg/css4-images/#image-set-notation).
> 
> Ah, right, well, not entirely valid, since 'x' is not a a defined unit identifier, while 'dppx' is. If we're following the spec, 'dppx' probably should be given preference over 'x' when serializing, at least until the CSSWG admits 'x' as a legitimate synonym for 'dppx'.
> 
> In any case, what cssText should return for a specified (inline) style is rather ambiguous, since it isn't well specified as to whether any canonicalization should occur or not when serializing this property value, i.e., when serializing an <image-set>.
> 
> But I agree it is a bug to return a unit-less dimension.

Note also the extra ',' between the url and scale factor which makes the string not parse at all.

I assume that at a minimum, we can agree that it's always a bug whenever a string that comes out of cssText causes a parse error (i.e. is ignored) when written back to cssText.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.