-
Notifications
You must be signed in to change notification settings - Fork 718
[css-overscroll-behavior] Merge overscroll-behavior specification #2179 #2997
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
Merged
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
Typo fixes
Small editing changes
Also make some small grammar fixes.
Update README title and add link to specification
Fixes issue w3c#8
Answer security privacy questionnare
- Closed a few open tags - Define local boundary action directly and remove explicitly linking them to 'local' - Don't auto link in propetydef which causes link issue. Other CSS specs do it this way - Make link to contain be specific
Create a new motivating example section and move existing example there. Also added two other examples related to other usecases of the API. Add simple css markup for each example scenario. Also formatted all lines to wrap @ 100 for consistency.
Clarify that contain prevents navigation.
Fix link issues
Add more motivating examples
scroll-boundary-behavior-x and scroll-boundary-behavior-y are longhand properties that accept keyword values (contain | none | auto). The computed value should be as specified. 'Computed value: see individual properties' only makes sense for shorthand properties, not longhands.
The syntax for scroll-boundary-behavior did not support distinct values for scroll-boundary-behavior-x and scroll-boundary-behavior-y. resolves w3c#18
Computed value as specified for longhands
Shorthand syntax when -x and -y values distinct
This ensures BS generates the correct issue link.
Specify Repository metadata
Update README to use overscroll-behavior
|
Brings overscroll-behavior repo to csswg-drafts repo without losing history. This is achieved using `git merge --allow-unrelated-histories` which allows a merge commit to contain two commits that don't share any ancestor. Fix issue w3c#2179
9f0651a
to
9cab4ab
Compare
@tabatkins would you be able to do the merge for this please. |
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.
[css-overscroll-behavior] Merge overscroll-behavior specification #2179
Migrate overscroll-behavior specification from its own WICG repo to CSSWG repository.
To preserve the history of the original repository the merge was achieved using
git merge --allow-unrelated-histories
. For more details see my notes here: #2179 (comment)