Agreed that this would be nice to have. I'm assuming you need a sort order configurable by the user, right? Feel free to include a link to a non-AMP implementation so we can get a good idea of the UX.

This might be reasonably straightforward with single-page amp-live-list implementations, but it gets more complicated once it needs to square with pagination, since a single AMP page does not know about all the entries of a live blog—it only knows about the items contained on that page.

For instance, way a live blog were broken up across multiple pages. In newest-first order, this isn't an issue (new updates come in, and get slotted at the top of the amp-live-list). In oldest-first order, if the user is looking at page 1 of N>1, and a new update comes in, the update button would either need to

a) flip the order of the list to newest-first order and take the user to the top of the page
b) navigate the user to the bottom of page N

Or updates could be disabled in oldest-first order

There's also a question of how to toggle the sort order in a paginated situation. There would need to be a server call of some kind to fetch the data living on another page.

A good v1 for this might be to enable it for single-page implementations, and to explore options for paginated implementations as an enhancement.

cc/ @erwinmombay

amp-live-list sort order is not configurable #5396

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions