-
Notifications
You must be signed in to change notification settings - Fork 256
fix: Use layout index as fallback criterion for zIndex sorting #333
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
Open
veracioux
wants to merge
1
commit into
sst:main
Choose a base branch
from
veracioux:fix/zindex-respect-layout
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
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
Oops, something went wrong.
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.
I know this only runs when something changes, but in a long list for example that can be frequent. It seems like the opencode issue is that the "copied to clipboard" notification should just have a higher zIndex?
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.
This is a fix for a general issue, not just for the opencode issue. Opencode is just the first place I discovered it. For example if you look at this code:
https://github.com/veracioux/opentui-332-repro/blob/main/index.tsx#L7
If you remove the
Showelement around the innerbox, the issue isn't reproducible. I think this is confusing behavior and should be fixed.If you are concerned about performance, would you be ok with updating this map inside Renderable.add function and only reading it in ensureZIndexSorted?
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.
@kommander Do you think it would be ok to implement it that way?
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 would prefer something like that, yeah.
I think I am failing to understand what the issue is actually. Isn't the "copied to clipboard" toast positioned absolutely? I wonder why the layout order should influence that then.
Could we maybe have that issue reproduced in a test? Can be a snapshot test so ensure it is rendered in expected order.
Uh oh!
There was an error while loading. Please reload this page.
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.
In browsers the expectation is that the stacking order is determined by zIndex, but if two elements have the same zindex (or undefined), then the element that comes later in the layout should be displayed over the element that comes before. Absoluteness has nothing to do with it.
Open this minimalistic index.html in a browser to see what I mean. Btw, the behavior is the same with position: static instead of relative.
I think opentui should do the same.
I'll try to create a test reproducing the issue like https://github.com/veracioux/opentui-332-repro does.