Closed
Bug 1380902
Opened 8 years ago
Closed 8 years ago
FF does not implement all SVG floating point number formats
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tshinnic, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170628075643
Steps to reproduce:
Created SVG path strings using f.p. format "nnn." as documented in the now 16 year-old specification.
Actual results:
Path strings using number formats "nnn", "nn.nn", or ".nnn" were displayed, but any string employing number format "nnn." is rejected without display.
Expected results:
All number formats in the SVG specification should be accepted and understood.
Among the example tests at https://codepen.io/tshinnic/full/XgOvVP/ are:
<path d="M 30 75 L 70 75" stroke-width="5" stroke="red" fill="none" />
<path d="M 30 75 L 70 75. " stroke-width="5" stroke="black" fill="none" />
If the format "nnn." is supported then a black line will hide the red line. (This is in the style of the Web Platform Tests) Only the red line is displayed unfortunately.
As mentioned in the note at https://github.com/w3c/svgwg/issues/331 , FireFox and Chrome appear to have implemented only the number formats described by CSS. SVG has always had a fourth format beyond the CSS spec. The more recent implementation of SVG in Edge (and after all the harassment they got for not following standards) *does* implement all the SVG number formats.
Please read that note at https://github.com/w3c/svgwg/issues/331 and additionally review the test demo at https://codepen.io/tshinnic/full/XgOvVP/
This is embarrassing all around. The 'nicest' resolution would be for FireFox and Chrome to say 'oops' and implement the rest of the SVG spec. That there were no tests and everyone (?) has worked-around the unimplemented spec may drive a vendor push to drop the number format from the SVG spec.
Updated•8 years ago
|
Component: Untriaged → SVG
Product: Firefox → Core
Comment 1•8 years ago
|
||
Unfortunately the SVG specification is inconsistent. Numbers normally require a digit per https://www.w3.org/TR/SVG/types.html#DataTypeNumber I really don't think we want to pass in a this is a path number flag.
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•