[wp-trac] [WordPress Trac] #50105: Remove infinite scrolling behavior from the Media grid

[WordPress Trac]

#50105: Remove infinite scrolling behavior from the Media grid
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  5.8
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-           |     Focuses:  ui, accessibility,
  screenshots needs-testing needs-   |  javascript
  testing-info early                 |
-------------------------------------+-------------------------------------

Comment (by francina):

 Thanks @joedolson!
 Makes sense to ship this as an MVP and then iterate with pagination or any
 other solution that makes this accessibile, easly understandable and
 usable 🙌

 > Jump to first attachment loaded in this request" seems awfully verbose.

 I'll take awfully verbose over unclear anytime, but this is only my
 opinion of course. "Request" is a technical term, end-users will not
 relate to it probably.

 "Jump to the first file uploaded in the previous XX" where XX could be
 "operation, load, command" perhaps?
 I am also trying to think about how that would sound in Italian "Vai al
 primo file caricato dopo l'ultima operazione".
 I am adding a reminder to myself to ping copywriters and polyglots to come
 up with a reasonable text :)

 ----

 Regarding the patch, it applies cleanly. What I meant by "almost" referred
 to known bug of the total counter. But I wasn't clear on communicating
 that, my bad.

 ----

 And finally the npm command. This ticket doesn't have testing
 instructions, hence the `needs-testing-info` keyword added.
 Since WordPress 5.6, the release squad has a testing focus lead: it was
 observed that not many tickets have clear testing instructions added, in
 the form of a list of steps needed.
 I did figure out what to do and noticed that when you use `wordpress-
 develop` you need an additional `npm run dev`after the patch is applied.
 But it is only for people that test with that specific environment.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50105#comment:73>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform