You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When inserting a query loop block there's a prompt to choose a pattern for the block. The subsequent modal has icons for list and grid views at the bottom, but if you click the grid icon, the Choose button disappears so the pattern cannot be selected.
Step-by-step reproduction instructions
Create a new page or page template
Insert the Query Loop block
Click Choose to select a pattern
Click the Grid icon at the bottom of the modal
Note that the "Choose" button that was visible on the List view, disappears when switching to Grid view
Screenshots, screen recording, code snippet
Environment info
WordPress 6.0, Twenty Twenty-Two v1.2
Can replicate with and without Gutenberg v13.2.2 activated
Firefox 100.0.2 on MacOS 12.3.1
Reported by a WordPress.com user with Chrome 101 on Windows 10
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
The text was updated successfully, but these errors were encountered:
Ah, now I get it, @Mamaduka. It's not list-patterns and grid-patterns, but a list-view and grid-view of the available patterns. The user who reported this on WordPress.com and I both got this wrong, so yeah, it would be good if that could be a bit more clear :D
Description
When inserting a query loop block there's a prompt to choose a pattern for the block. The subsequent modal has icons for list and grid views at the bottom, but if you click the grid icon, the Choose button disappears so the pattern cannot be selected.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Environment info
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
The text was updated successfully, but these errors were encountered: