Make WordPress Core

Opened 3 years ago

Closed 9 months ago

#53536 closed defect (bug) (wontfix)

Media Library: Quick 'Jump to first loaded item' redirecting to wrong item on 5.8-beta4-51247

Reported by: alanjacobmathew's profile alanjacobmathew Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.8
Component: Media Keywords: needs-patch
Focuses: ui Cc:


v: 5.8-beta4-51247 Theme: Twenty Twenty One. No plugins Installed

The 'Jump To First Loaded Item' button found in the media library doesn't redirect to the very first(on the top) item in the library and only to the first item in the newly loaded set.

To reproduce:
1: Add 50-60 images in the media library
2: Reload the page and click on Load More' button.
3: Click on 'Jump to First Loaded item' button

Currently it loads to the 41st item, 81st item, 121st item .. respectively whenever the user loads more images.

Expected output: On clicking it goes to the very 1st item.

Attachments (1)

Jump to first loaded item.gif (3.9 MB) - added by alanjacobmathew 3 years ago.
Media Library

Change History (11)

3 years ago

Media Library

#1 @SergeyBiryukov
3 years ago

  • Milestone changed from Awaiting Review to 5.8

#2 @desrosj
3 years ago

  • Component changed from Gallery to Media
  • Keywords needs-patch added

#3 @desrosj
3 years ago

  • Version set to trunk

I had noticed this in my testing as well. After looking at it a bit, I think that "Jump to the first loaded item" is meant to jump to the first item in the new set. But for some reason I'm finding this confusing and unexpected.

I'm thinking that this can be punted and improving this can be explored for 5.8.1.

@joedolson @antpb @adamsilverstein Any "quick win" ideas to address this in 5.8? If not, let's punt.

#4 @joedolson
3 years ago

It's working correctly; it is supposed to jump to the first item in the newly loaded set of items.

Any suggestion on an alternate button text that might make this more clear? I don't see a strong reason to revert this, given that it's working correctly; it might just need some additional clarity in the button text.

#5 @joedolson
3 years ago

Oh; I misunderstood. You said 'punt' and my mind said 'revert'. No, I don't think this ticket needs to be handled before 5.8.1.

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.

3 years ago

#7 @JeffPaul
3 years ago

  • Milestone changed from 5.8 to Future Release

Given this will likely result in a string change, that no confirmed approach or copy has been agreed to, that no patch/PR exists, and with no clear owner I'm inclined to punt this to Future Release. This ticket seems like we could get to quick agreement on approach and pulled back into a numbered milestone at that point.

This ticket was mentioned in Slack in #core-media by azaozz. View the logs.

3 years ago

This ticket was mentioned in Slack in #core-media by antpb. View the logs.

3 years ago

#10 @joedolson
9 months ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

With no additional concerns about this in the last two years, I think this is a non-issue. Closing as wontfix.

Note: See TracTickets for help on using tickets.