Skip to content

Commit 9798050

Browse files
committed
[css-ui-3] reorder sentences, reduce duplication in transition request
1 parent c21cf84 commit 9798050

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

css-ui-3/transition-pr-2017-11.md

+4-6
Original file line numberDiff line numberDiff line change
@@ -29,20 +29,18 @@ First Tuesday or Thursday after a sucessful transition decision.
2929
[Changes since the 2017-10-25 Candidate Recommendation](https://drafts.csswg.org/css-ui-3/#changes)
3030
<!-- no substantive changes -->
3131

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.
3333

3434
* Clarify (as a SHOULD) the implications of text-overflow on pointer events to capture implementor consensus (corresponding test).
3535
* Clarify that UAs may ignore the cursor property to reflect the UA’s UI state
3636
* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update).
3737
* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests).
3838

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-
4139
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.
4240

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,
4644
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).
4745

4846
Thus the editors and WG believe all four normative changes fall within the bounds allowed for a CR->PR transition.

0 commit comments

Comments
 (0)