-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Sticky Position: Try re-enabling non-root sticky position #49321
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
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
877f788
Sticky Position: Try re-enabling non-root sticky position, and add a …
andrewserong 80be3a6
Fix whitespace
andrewserong 95a5504
Ensure the position visualizer does not interfere with the ability to…
andrewserong d78322c
Ensure resizing the block editor will update the block popover dimens…
andrewserong 9e5d9bc
Try simplifying the display logic so it always shows the visualizer i…
andrewserong 5ad63a2
Small code quality tweaks
andrewserong c4a105d
Try dotted outline, subtle display on focus and hover label
andrewserong 9311103
Fix help text and spacing
andrewserong c995d72
Update visualizer to only display on hover
andrewserong b9e7b37
Remove visualizer
andrewserong File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Small code quality tweaks
- Loading branch information
commit 5ad63a240fa8809efb825772c073640890733217
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Crazy idea: could we use this client id to instead inject a style in the DOM like
#block-clientid :has(.ist-sticky.is-selected) { outline: 1px solid grey}or whatever?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, that is a clever idea — I can't remember why exactly, but I think from memory there was a preference to try to use popovers so that we don't accidentally collide with any styles that a theme might have for a particular block. It could be to ensure that the visualizers / popover always displays its CSS styling in addition to whatever might be set on the parent block (that we can't quite know) rather than overriding anything. Worth playing with though!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I picked outline because it's very unlikely that it gets used for block styling, as it's mostly a property applied on focus. Though if the popover calculations are performant I suppose it's not really an issue.