Description
I do not believe there are meaningfull cases that warrant a fix for the following, if it is an actual bug. My motivation for creating this issue is also to use it for code documentation. I have searched for existing issues with "scientific notation integer", with no success. I also searched for a WPT.
order: 1e0
is parsed as invalid in browsers because order
should be an <integer>
.
I do not have a high education in maths: perhaps a number representing an integer but expressed with the scientific notation must not be considered as an integer.
Otherwise, step 5.3 of consume a number could be replaced after step 6 by evaluating if repr
is an integer. I do not know how this evaluation can be translated into spec/WebIDL terms.
Perhaps it can not be fixed because it would break parsing eg. <signless-integer>
and <signed-integer>
.
Or it may simply be decided that it is not worth to be fixed.