-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
fix(web): prevent thumbhashes from covering search bar #20720
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
Conversation
Deploying preview environment to https://pr-20720.preview.internal.immich.cloud/ |
{#if (!loaded || thumbError) && asset.thumbhash} | ||
<canvas | ||
use:thumbhash={{ base64ThumbHash: asset.thumbhash }} | ||
class="absolute object-cover" |
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.
also note the z index class has been removed
I'm going to find out why we define the thumbhash in two places and which is the right one to use, and whether it breaks displaying errors. |
So from testing quickly, it's not making anything worse. It looks like thumbhashes already hide the error state. I'll try and clean it up though as I'm here. |
440fffd
to
3f42693
Compare
The thumbhash had a z-index setting which meant it would cover the search bar, and would always cause weird animations when scrolling up in search results. This is fixable by removing the z-index and moving it in front the other elements to get a naturally higher higher z-index preference.
3f42693
to
d1dc321
Compare
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.
Nice fix!
Description
The thumbhash had a z-index setting which meant it would cover the search bar, and would always cause weird animations when scrolling up in search results.
This is fixable by removing the z-index and moving it in front the other elements to get a naturally higher higher z-index preference.
How Has This Been Tested?
I've tested locally, but I can also test on the preview instance too.
Screenshots (if appropriate)
Before:
After:
Checklist:
src/services/
uses repositories implementations for database calls, filesystem operations, etc.src/repositories/
is pretty basic/simple and does not have any immich specific logic (that belongs insrc/services/
)