Closed
Bug 775941
Opened 12 years ago
Closed 12 years ago
'order' is a <number>, not an <integer> (nevermind, now it's an <integer> after all)
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: dholbert, Assigned: dholbert)
References
()
Details
(Keywords: dev-doc-complete)
It appears that the flexbox <order> property changed at some point to take <number> values, not <integer> values. (It used to be specced as taking <integer>, like z-index) http://dev.w3.org/csswg/css3-flexbox/#order The patch that landed for <order> in bug 696253 made it take <integer>, but I need to change it to take <number> instead.
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Comment 1•12 years ago
|
||
(Asking for clarification if the '<number>' choice is really intentional, here: http://lists.w3.org/Archives/Public/www-style/2012Jul/0476.html )
Comment 2•12 years ago
|
||
Adding dev-doc-needed. We document it as <number> if it goes back to <integer> (which we'll lead to this bug to go to RESOLVED INVALID) we will need to update the doc and we'll be notified thanks to the keyword. If not, we'll switch the keyword to dev-doc-complete when this bug get RESOLVED FIXED ;-)
Keywords: dev-doc-needed
Assignee | ||
Comment 3•12 years ago
|
||
Yay, spec has been updated to make it an <integer>, so my code turned out to be right after all. :) http://lists.w3.org/Archives/Public/www-style/2012Jul/0607.html So, resolving as INVALID. I also updated the new (editable) KUMA-based MDN instance with s/number/integer/. https://developer-new.mozilla.org/en-US/docs/CSS/order --> updating to dev-doc-complete.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Keywords: dev-doc-needed → dev-doc-complete
Resolution: --- → INVALID
Summary: 'order' is a <number>, not an <integer> → 'order' is a <number>, not an <integer> (nevermind, now it's an <integer> after all)
You need to log in
before you can comment on or make changes to this bug.
Description
•