Latest edits/resolutions, see the editors draft:
Closed issues, see:
This issues page is key to the work mode of CSS3-UI.
Steps to PR
Continue resolving/editing per General Steps
√ Resolve all issues 2014 or before and make edits
Put out call for test cases - noting substantial feature stability
Publish draft with all 2014 or before issues resolved
Resolve/reject new 2015 issues as appropriate for an LCCR
Get feature coverage in test cases (or consider dropping at-risk features)
Collect/process issues raised from test / implementation interactions
Publish a PR with subset of features that interoperate, dropping at-risk features as necessary
General steps in rough order:
Issue new: 101
- Raised by
- Tantek Çelik
- Proposed Resolution :
- Status :
Issues Pending edits
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 Pending dependent edits
Issues that are resolved, and require no specific edits, but are depending on edits for another issue to be completed.
text-overflow for non-latin scripts
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.”
text-overflow atomic inlines that would overlap the ellipsis
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).
css3-ui additional spec improvements
Consider adding clarifying examples in spec
, adding tests. (per Issue 22)
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