immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-25 03:12:21 +03:00
Code Issues 783 Packages Projects Releases 12 Wiki Activity

Going back to search results from a fullscreen-displayed photo - always returns to the start of the search results list #3085

New Issue
Closed
opened 2026-02-05 07:40:20 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 07:40:20 +03:00
Owner
Copy Link

Originally created by @dariuszszyc on GitHub (May 9, 2024).

The bug

App moves to the beginning of the search results when returning from a clicked photo.

The OS that Immich Server is running on

not-relevant

Version of Immich Server

1.103.1

Version of Immich Mobile App

latest

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

not-relevant

Your .env content

not-relevant

Reproduction steps

1. Use the search functionality to find some photos.
2. Scroll down a bit and click any photo - it will open full screen
3. Now you want to return to the list to click another photo you saw next to the previous one - so you click "back/arrow" button on the top left
4. As a result - you are back to the top of the search results list and you have to scroll down again to the place where you were.

It makes it hard to use the searching functionality as every time you click a photo and return - you have to start from the top.

On mobile - when you return from a fullscreen photo display - you are still in the place where you were, seeing the photo that you just clicked.

Relevant log output

No response

Additional information

No response

Originally created by @dariuszszyc on GitHub (May 9, 2024). ### The bug App moves to the beginning of the search results when returning from a clicked photo. ### The OS that Immich Server is running on not-relevant ### Version of Immich Server 1.103.1 ### Version of Immich Mobile App latest ### Platform with the issue - [ ] Server - [X] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML not-relevant ``` ### Your .env content ```Shell not-relevant ``` ### Reproduction steps ```bash 1. Use the search functionality to find some photos. 2. Scroll down a bit and click any photo - it will open full screen 3. Now you want to return to the list to click another photo you saw next to the previous one - so you click "back/arrow" button on the top left 4. As a result - you are back to the top of the search results list and you have to scroll down again to the place where you were. It makes it hard to use the searching functionality as every time you click a photo and return - you have to start from the top. On mobile - when you return from a fullscreen photo display - you are still in the place where you were, seeing the photo that you just clicked. ``` ### Relevant log output _No response_ ### Additional information _No response_
OVERLORD commented 2026-02-05 07:40:26 +03:00
Author
Owner
Copy Link

@nick-roux commented on GitHub (May 9, 2024):

Seeing the same issue on 1.103.1.

@nick-roux commented on GitHub (May 9, 2024): Seeing the same issue on 1.103.1.
OVERLORD commented 2026-02-05 07:40:29 +03:00
Author
Owner
Copy Link

@atlas-shrugged08 commented on GitHub (May 14, 2024):

plus 1, seeing the same on 1.104.
It makes search less usable as every single time you click on something in a search result you are taken back to the top.

edit: I just found that this happens only on google chrome (for me at least) chrome is my primary browser but when i tried this on Safari, I could not reproduce the behavior. Also works on the ios app.

@atlas-shrugged08 commented on GitHub (May 14, 2024): plus 1, seeing the same on 1.104. It makes search less usable as every single time you click on something in a search result you are taken back to the top. edit: I just found that this happens only on google chrome (for me at least) chrome is my primary browser but when i tried this on Safari, I could not reproduce the behavior. Also works on the ios app.
OVERLORD commented 2026-02-05 07:40:33 +03:00
Author
Owner
Copy Link

@danieldietzler commented on GitHub (May 20, 2024):

Duplicate of #6052

@danieldietzler commented on GitHub (May 20, 2024): Duplicate of #6052
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#3085
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?