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
Photo Viewer: Searching then browsing shows the wrong images #1343
Comments
Interesting, maybe this goes somehow back in your browser history? |
I get the same results in a new private browser window. Results seem inconsistent. For example i sort my search results from oldest to newest it behaves as expected, if i then display search results from newest to oldest, doesnt work correctly |
You will notice in the video below, the images that are browsed, don't match the search results |
I face the exact same issue (docker install on my Unraid server) |
docker install on unraid here as well |
@graciousgrey can test it tomorrow |
I can reproduce it. It happens only for some photos of my search result and it does not happen if I click reload before browsing photos in fullscreen mode @darkenbula @guim31 could you test the following:
Thank you! |
Best i can tell, if i close my browser and start over from scratch,. i get the unintended behaviour no matter where i start viewing the pictures from If i refresh the page F5, it behaves correctly |
The observed behaviour appears to be a timing issue when opening an image shortly after the search query / filter was changed, thus it wasn't reproducible in a dev environment with only a few images.
If i perform a search across my library for something like 'cat' for example, the search will return expected results of cat pictures. If i click on the first picture to view it and then use the right arrow i would expect it to cycle through the search results. Instead it will browser by date, so if the first returned search result is from march 6, using the right arrow to move to the next photo will cycle in reverse order through pictures from that date.
The text was updated successfully, but these errors were encountered: