You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: css-ui-3/transition-pr-2017-11.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -29,20 +29,18 @@ First Tuesday or Thursday after a sucessful transition decision.
29
29
[Changes since the 2017-10-25 Candidate Recommendation](https://drafts.csswg.org/css-ui-3/#changes)
30
30
<!-- no substantive changes -->
31
31
32
-
The following changes were judged by the CSS-WG to be within the bounds allowed for a CR->PR transition:
32
+
There are 4 normative changes, all based on feedback from actual implementations on a few subtleties of how they had implemented the features.
33
33
34
34
* Clarify (as a SHOULD) the implications of text-overflow on pointer events to capture implementor consensus (corresponding test).
35
35
* Clarify that UAs may ignore the cursor property to reflect the UA’s UI state
36
36
* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update).
37
37
* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests).
38
38
39
-
These are normative changes, but they are all based on feedback from actual implementations on a few subtleties of how they had implemented the features.
40
-
41
39
The first 3 changes are are small tweaks and cannot make an implementation that conformed to the spec prior to the changes become non-conformant.
42
40
43
-
The 4th change could theoretically impact conformance, but in practice does not.
44
-
Zero known implementations (Gecko/Edge/Webkit/Blink/Presto) conformed with the previous wording (the [issue 1598 was openly reviewed and discussed](https://github.com/w3c/csswg-drafts/issues/1598) for several months),
45
-
while multiple implementations pass tests and interoperate with the change,
41
+
The 4th change could theoretically impact conformance, but in practice does not.
42
+
Zero known implementations (Gecko/Edge/Webkit/Blink/Presto) conformed with the previous wording (the [issue 1598 was openly reviewed and discussed](https://github.com/w3c/csswg-drafts/issues/1598) for several months),
43
+
while multiple implementations pass tests and interoperate with the change,
46
44
and all others for which conformance was not affected (did not pass before or after) agreed to update to conform to the new wording (over the old).
47
45
48
46
Thus the editors and WG believe all four normative changes fall within the bounds allowed for a CR->PR transition.
0 commit comments