forked from w3c/csswg-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Add the <syntax> Production #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
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
…on of 'acceptable anchor element'.
…make it more obvious.
Matches the expectations from tests See w3c#5386
This particular change is already covered in the L3 changelog, which we refer to, so it should not be duplicated.
…st arg reorderable. w3c#10317
…tion-try-options value. w3c#10320
07db605 changed the term "involved in a view transition" to "captured in a view transition". Update accordingly.
Signed-off-by: Jens Oliver Meiert <jens@meiert.com>
Having incomping links to removed parts of the sections go to the Changes section helps readers find where the text has gone. See w3c#10472
1. By depending on the animation rules defined in https://drafts.csswg.org/css-contain-3/#content-visibility-animation the step-end and step-start values are not needed. 2. 2. By depending on the change in whatwg/html#10265 (comment) and whatwg/html@fb3033a the `display: block` is no longer needed.
…w3c#10376) * [css-scroll-snap-2] Set pseudo snap Targets to their owning elements. This specifies the resolution from w3c#10175 that when the targets of a snap event are pseudo elements, the snap event should the owning elements of the pseudo-elements as snap targets. * Bikeshed fixes, terminology --------- Co-authored-by: David Awogbemila <awogbemila@chromium.org> Co-authored-by: Tab Atkins Jr <jackalmage@gmail.com>
This specifies the resolution on w3c#10173 making snap events bubble when fired at the document. Co-authored-by: David Awogbemila <awogbemila@chromium.org> Co-authored-by: Tab Atkins Jr <jackalmage@gmail.com>
* Specify scroll-start-target This adds details to the scroll-snap-2 spec[1] to specify scroll-start-target. [1] https://drafts.csswg.org/css-scroll-snap-2 * [css-scroll-snap-2]] Specify scroll-start-target * [css-scroll-snap-2] Specify scroll-start-target Define initial scroll position precedence in css-overflow-3. De-vaguify post-first layout scroll-start-target & point to document update process. Extract scroll-view position algorithm for standalone use. * [css-scroll-snap-2] Specify scroll-start-target Remove slight duplication. * [css-scroll-snap-2] Specify scroll-start-target Replace scroll-view with scroll-into-view. Mention and link css properties that change initial scroll position. --------- Co-authored-by: David Awogbemila <David Awogbemila> Co-authored-by: David Awogbemila <awogbemila@chromium.org> Co-authored-by: Tab Atkins Jr <jackalmage@gmail.com>
* [css-mixins] Add CSS Functions and Mixins specification To begin with, only @function is described. * bikeshed-clean * Generate missing Big Text. * "An at-function" -> "A function" There's apparently no right answer to "an at-foo" vs "a foo", but we can at least stay consistent within the same spec. * Resolve to the default value when the type is wrong. * Update css-mixins-1/Overview.bs --------- Co-authored-by: Tab Atkins Jr <jackalmage@gmail.com> Co-authored-by: Miriam Suzanne <miriam@oddbird.net>
@andruud were you planning to merge these changes as well? |
@mirisuzanne Yes, but I intentionally left it as an optional add-on to avoid doing too many things at once. I'll send the PR again against the main repo, and then we can review it there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.