fix: prefer current selection when css reverse seleting multiple matches #2571
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
|
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.
Previously, when a CSS selector matched multiple elements in Live Preview, we always picked the first match. That often caused a page jump (e.g., you’re editing near page 5, but the first match is on page 1), making CSS edits frustrating and sometimes impossible to do on the visible element.
Now, when a selector has multiple matches, we prefer the element you’re editing (or the closest matching parent/nearby match) instead of the first node. This keeps the selection local to what’s on screen, so inline CSS editing (and other CSS edits) usually won’t yank you to a different part of the page.