NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 345 - revise definitions of float datatypes to match current spec
revise definitions of float datatypes to match current spec
Classification: Unclassified
Component: HTML5 schema
All All
: P2 normal
Assigned To: Henri Sivonen
Depends on:
  Show dependency treegraph
Reported: 2008-12-07 16:20 CET by Michael[tm] Smith
Modified: 2009-01-12 14:24 CET (History)
0 users

See Also:

patch that implements proposed changes (2.68 KB, patch)
2008-12-07 16:22 CET, Michael[tm] Smith

Note You need to log in before you can comment on or make changes to this bug.
Description Michael[tm] Smith 2008-12-07 16:20:15 CET
<MikeSmith> hsivonen: you there?
<MikeSmith> hsivonen: I notice that the schema has both and, and that microsyntaxes for them differ
<MikeSmith> but the spec has only one definition for "valid floating point number"
<MikeSmith> which matches, but does not
<MikeSmith> so it seems like there only needs to be just one *.data.float pattern defined, and its definition should match the current one
<MikeSmith> same for and
<MikeSmith> and it seems that the definition for needs to be revised also
<MikeSmith> so, specifically that there should just be one definition for each, and that there definitions should be w:float-exp, w:float-exp-positive, with the new addition of w:float-exp-non-negative
<MikeSmith> anyway, I'll file a bug at
<MikeSmith> also, as far as the definition of float, the spec allows either "E" or "e", but the regexp in the schema comment restricts it to "e" only
Comment 1 Michael[tm] Smith 2008-12-07 16:22:51 CET
Created attachment 4 [details]
patch that implements proposed changes
Comment 2 Michael[tm] Smith 2009-01-12 14:24:15 CET
This was fixed in r370.