Skip to content

Commit

Permalink
add+clarify cursor auto change detail; link issue
Browse files Browse the repository at this point in the history
  • Loading branch information
tantek committed Nov 2, 2017
1 parent f18fe8f commit c21cf84
Showing 1 changed file with 9 additions and 5 deletions.
14 changes: 9 additions & 5 deletions css-ui-3/transition-pr-2017-11.md
Expand Up @@ -27,7 +27,7 @@ First Tuesday or Thursday after a sucessful transition decision.
## Changes

[Changes since the 2017-10-25 Candidate Recommendation](https://drafts.csswg.org/css-ui-3/#changes)
<!-- no substantive chnges -->
<!-- no substantive changes -->

The following changes were judged by the CSS-WG to be within the bounds allowed for a CR->PR transition:

Expand All @@ -36,12 +36,16 @@ The following changes were judged by the CSS-WG to be within the bounds allowed
* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update).
* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests).

These are normative changes, but they are small tweaks to take into account implementation feedback on a few subtleties of the features.
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.

The first 3 changes cannot make an implementation that conformed to the spec prior to the changes become non conformant.
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.

The 4th one arguably could, but implementations were in violation of the spec prior to the change (and not willing to align),
while we have more than 2 test-passing implementations after the change with the rest being willing to align.
The 4th change could theoretically impact conformance, but in practice does not.
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),
while multiple implementations pass tests and interoperate with the change,
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).

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

## Requirements satisfied

Expand Down

0 comments on commit c21cf84

Please sign in to comment.