Latest edits/resolutions, see the editors draft:
Closed issues, see:
Postponed issues:
See also:
This issues page is key to the work mode of CSS3-UI.
General steps in rough order:
The following are open issues in/with the 17 Jan 2012 CSS3-UI Working Draft, and/or the latest CSS3-UI Editor's Draft.
There are currently no known issues with this specification.
The following issues need an edit to be applied to the spec. Most of them have a WG resolution, and those that don't are editorial/non-controversial and don't need a resolution.
Issues that are resolved, and require no specific edits, but are depending on edits for another issue to be completed.
Q: Many non latin scripts use something else than 3 dots for the same effect as an ellipsis. How does this work?
A: The current editor's draft allows implementations to use something other than 3 dots:
“Implementations may substitute a more language/script-appropriate ellipsis character.”
from http://dev.w3.org/csswg/css3-ui/#text-overflow
Q: What should an implementation do when an atomic inline element would overlap the ellipsis marker?
A: Remove it (the atomic inline element(s)) to make room for the ellipsis marker per the CSS3-UI spec (and Opera and IE9 appear to do this already).
Leaving resolved subheadings here with forward links to W3C wiki to preserve external links to fragments.
Includes closed and rejected issues as well which have been moved