Add note for anchor positioning fallbacks behaviour #41419
+3
−0
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
Developer's intuition for how anchor positioning fallbacks works does not match the specced behaviour, as demonstrated in [this poll](https://mastodon.social/@Meyerweb/115106404124445073) The spec is not expected to change - w3c/csswg-drafts#12682 - so a note to developers can help prevent this pitfall.
github-actions
bot
added
Content:CSS
|
Preview URLs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Adding a note for position-try-fallbacks to explain that the element does not revert to its original position when available space is restored.
Motivation
Developer's intuition for how anchor positioning fallbacks works does not match the specced behaviour, as demonstrated in this poll
The spec is not expected to change - w3c/csswg-drafts#12682 - so a note to developers can help prevent the pitfall of not understanding why it's not going back to the starting position.