[Bug 28148] Improve parsing of numbers for coords attribute

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28148

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> ---
> For floating point arguments between 0 and 1 without a leading 0, the floating
> point value simply drops the decimal.

Do UAs implement that?  Because I don't think Gecko does: we seem to chunk up
the list on whitespace+commas and then just atoi the things in between, so .100
turns into 0.

> there's no reason why the coords attribute shouldn't accept a list of floating
> point values

Except for possible compat issues, right?  Again, would be good to know what
actual UAs do here.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 6 March 2015 02:30:28 UTC