mark at-risk features in a new snapshot#449
Merged
plehegar merged 10 commits intow3c:gh-pagesfrom Apr 3, 2019
Merged
Conversation
gkatsev
commented
Mar 6, 2019
| <a href="https://github.com/web-platform-tests/wpt/tree/master/webvtt">test suite</a>. The Working | ||
| Group does not require that implementations are publicly available but encourages them to be so.</p> | ||
|
|
||
| <div data-fill-with="at-risk"> |
Collaborator
Author
There was a problem hiding this comment.
this piece is the main change.
nigelmegitt
requested changes
Mar 14, 2019
Contributor
nigelmegitt
left a comment
nigelmegitt
left a comment
There was a problem hiding this comment.
It will be helpful to readers, and to us later, if it is really clear exactly which spec text will be removed if each at risk feature is to be removed. It looks pretty clear for the second two features, but not for the first one.
…from at-risk section
nigelmegitt
approved these changes
Mar 14, 2019
Member
|
Transition request: w3c/transitions#126 |
plehegar
approved these changes
Mar 28, 2019
Co-Authored-By: gkatsev <git@gkatsev.com>
Co-Authored-By: gkatsev <git@gkatsev.com>
Co-Authored-By: gkatsev <git@gkatsev.com>
Co-Authored-By: gkatsev <git@gkatsev.com>
Collaborator
Author
|
I've accepted the updates. |
Contributor
|
The previous version needs to be updated too, as does the pub date (15 April) which is too late for a 2 May deadline for comments. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Made a new snapshot for 2019-03-06 and manually applied 2c06667 and c9100e0.
Then I marked collision avoidance with snap-to-lines false,
::cue-regionand::cue-region()pseudo-elements, and:pastand:futurepseudo-classes as at-risk.STYLE block is no longer marked at risk because I have a prototype that would be completed during the mandatory 28-day waiting period after this snapshot is published as the new CR.