WordPress / gutenberg

The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
https://wordpress.org/gutenberg/
Other
10.3k stars 4.11k forks source link

My Patterns: the pagination doesn't keep the state after click on a pattern #59003

Open miksansegundo opened 6 months ago

miksansegundo commented 6 months ago

Description

The pagination doesn't keep the state in My Patterns page.

I expected that after I use the pagination to see a page, I can click on a pattern, to preview it and then click the < back button on the sidebar of the pattern detail to come back to the same page.

Step-by-step reproduction instructions

Screenshots, screen recording, code snippet

https://github.com/WordPress/gutenberg/assets/1881481/6370c2a1-820c-42ad-8c87-14a270cc6941

Environment info

Gutenberg: v17.7.0-rc.1

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

miksansegundo commented 6 months ago

This same issue affects any Data View options and filters.

I expected those to be also kept when I preview, or even edit a pattern, and I go back to the My patterns via the < back button.

Filters View Options
Screenshot 2567-02-14 at 17 24 13 Screenshot 2567-02-14 at 17 18 36
annezazu commented 6 months ago

cc @ntsekouras

ntsekouras commented 6 months ago

Yeah, right now that's not possible. There are some discussions about adding some of the params in the URL that would resolve this. We do this for the layout type right now only(grid, table, etc..). There are some nuances with the custom views exploration that could come from database for example and in that case we have two sources of truth, but will probably prioritize the url query params.

colorful-tones commented 6 months ago

will probably prioritize the url query params.

This sounds like a good plan. We’ll need URL query params soon. 👍

annezazu commented 6 months ago

Removing this from the 6.5 board since there's not an immediate solution to implement as shown above and due to the voting that happened in the async triage session this week.