|
| 1 | +(from [pr transitions](https://www.w3.org/Guide/transitions?profile=PR) ) |
| 2 | +<!-- read that link to understand how to fill in the template --> |
| 3 | + |
| 4 | +# Transition request for PR: TITLE. |
| 5 | + |
| 6 | +## Document title, URIs, and estimated publication date |
| 7 | + |
| 8 | +CSS Basic User Interface Module Level 3 (CSS3 UI) |
| 9 | + |
| 10 | +https://drafts.csswg.org/css-ui-3/ |
| 11 | + |
| 12 | +First Tuesday or Thursday after a sucessful transition decision. |
| 13 | + |
| 14 | +## The document Abstract and Status sections |
| 15 | + |
| 16 | +[abstract](https://drafts.csswg.org/css-ui-3/#abstract) |
| 17 | + |
| 18 | +[status (as ED)](https://drafts.csswg.org/css-ui-3/#status) |
| 19 | + |
| 20 | + |
| 21 | +## Decision to request transition |
| 22 | + |
| 23 | + - RESOLVED: Take CSS UI 3 to PR. |
| 24 | + |
| 25 | +[minutes, 2017-10-25 telcon](https://lists.w3.org/Archives/Public/www-style/2017Oct/0044.html) |
| 26 | + |
| 27 | +## Changes |
| 28 | + |
| 29 | +[Changes since the 2017-10-25 Candidate Recommendation](https://drafts.csswg.org/css-ui-3/#changes) |
| 30 | +<!-- no substantive chnges --> |
| 31 | + |
| 32 | +The following changes were judged by the CSS-WG to be within the bounds allowed for a CR->PR transition: |
| 33 | + |
| 34 | +* Clarify (as a SHOULD) the implications of text-overflow on pointer events to capture implementor consensus (corresponding test). |
| 35 | +* Clarify that UAs may ignore the cursor property to reflect the UA’s UI state |
| 36 | +* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update). |
| 37 | +* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests). |
| 38 | + |
| 39 | +These are normative changes, but they are small tweaks to take into account implementation feedback on a few subtleties of the features. |
| 40 | + |
| 41 | +The first 3 changes cannot make an implementation that conformed to the spec prior to the changes become non conformant. |
| 42 | + |
| 43 | +The 4th one arguably could, but implementations were in violation of the spec prior to the change (and not willing to align), |
| 44 | +while we have more than 2 test-passing implementations after the change with the rest being willing to align. |
| 45 | + |
| 46 | +## Requirements satisfied |
| 47 | + |
| 48 | +There is no specific requirements document for this specification. The work |
| 49 | +is within the scope defined in the CSS WG's charter, |
| 50 | + |
| 51 | +## Dependencies met (or not) |
| 52 | + |
| 53 | +<!-- no normative references to a Rescinded Recommendation --> |
| 54 | + |
| 55 | +The following normative reference to W3C documents is not yet at CR: |
| 56 | + |
| 57 | +* [CSS-COLOR-4](https://www.w3.org/TR/css-color-4/), in order to refer to a precise definition of a concept that exists implicitely since CSS21. |
| 58 | + |
| 59 | +Additionally, the following normative references to W3C documents are at CR but not yet at PR: |
| 60 | + |
| 61 | +* [CSS-VALUES-3](https://www.w3.org/TR/css-values-3/), in order to define the grammar of properties using newer terminology anchors that those of CSS21. |
| 62 | +* [CSS-WRITING-MODES-3](https://www.w3.org/TR/css-writing-modes-3/), in order to refer to newer definitions of bidi terms than those of CSS21. Note that this specification is also almost ready to enter PR. |
| 63 | +* [CSS3-BACKGROUND](https://www.w3.org/TR/css3-background/), in order to refer to the border-radius property, which has been interoperably implemented in all major browser engines for many years. |
| 64 | +* [CSS3-IMAGES](https://www.w3.org/TR/css3-images/), in order to refer to updated definitions of concepts already present in CSS21, and to more precise definition of how image sizing in CSS should work than available in CSS21. |
| 65 | +* [SVG2](https://www.w3.org/TR/SVG2/), in order to reuse new terminology about existing behavior (loading an SVG file without script nor external references). |
| 66 | + |
| 67 | +## Wide Review |
| 68 | + |
| 69 | +This specification has been in development over many years (since 2002), |
| 70 | +and has been mostly stable since 2015. |
| 71 | +Over its development period, it has received extensive feedback from numerous parties, |
| 72 | +implementors or otherwise. |
| 73 | + |
| 74 | +Explicit calls for horizontal reviews were sent, |
| 75 | +the [latest one](https://lists.w3.org/Archives/Public/public-review-announce/2017Mar/0002.html) being for the current draft. |
| 76 | + |
| 77 | +There has now been additional implementation feedback from multiple browsers. |
| 78 | +All current feedback has been addressed and collected in the latest Disposition |
| 79 | +of Comments. |
| 80 | + |
| 81 | +## Issues addressed |
| 82 | + |
| 83 | +The [Disposition of Comments](https://drafts.csswg.org/css-ui-3/issues-2017-2) shows 9 issues since the last CR update. |
| 84 | +The [previous disposition of Comments](https://drafts.csswg.org/css-ui-3/issues-2015-2017) showed 12 issues, |
| 85 | +and [the one before](https://drafts.csswg.org/css-ui-3/issues-2012-2015) showed 103 issues. |
| 86 | + |
| 87 | +All are resolved. |
| 88 | + |
| 89 | + |
| 90 | +## Formal Objections |
| 91 | + |
| 92 | +None |
| 93 | + |
| 94 | +## Implementation |
| 95 | + |
| 96 | +[Final implementation report](https://drafts.csswg.org/css-ui-3/implementation-report) |
| 97 | + |
| 98 | +The [testsuite](https://test.csswg.org/harness/results/css-ui-3_dev/grouped/) shows that |
| 99 | +203 of 203 required tests meet CR exit criteria. |
| 100 | + |
| 101 | +## Patent disclosures |
| 102 | + |
| 103 | +[none](https://www.w3.org/2004/01/pp-impl/32061/status) |
0 commit comments