Open mtias opened 1 year ago
Seems a good place to add mine also. I have plan to open dedicated issues in following days.
If this is not an appropriate place I will delete.
[ ] Feature - Block - Block / Spacer - should use the “theme.json” spacing scale, with fallback to custom value
Proposed Solution: Let user defines value of height as one of these:
- spacing scale (1-2-3-…-7 or what comes from theme.json)
- custom value (if user want to go custom)
[ ] Block - Attribute - Gradient and Duotone color picker should let pick semantic token from “theme.json”
Proposed Solution: Add Color Switcher at bottom side equal to “Solid” color
[ ] Block - Block / Navigation - “Block Spacing” should be renamed to “Space between items” or “Items distance” or “Items Gap”
[ ] Block - Block / Button - add ability to edit "hover" and "active" state
Could be good to have this also at "Editor" > "Styles" level, when user can override every default block settings.
Seems a good place to add mine also. I have plan to open dedicated issues in following days.
The first one on your list has been worked on, but it has stalled somewhat - https://github.com/WordPress/gutenberg/pull/44002.
I imagine there are also issues open somewhere for hover/active states 😄
I'm not sure about the other two suggestions, but worth checking for existing issues first.
We should allow "Group" to have the same "full height + width of the page that cover has.
It's already possible for a Group to be full height in this way, by setting a 100vh
minimum height. It's also possible for it to be full width via the alignment control. So I'm going to check that item off for now. We can easily uncheck based on the answer to the following question:
Should there be a toolbar shortcut for the full-height option as there is in the Cover block? I'd learn towards no because it seems like a feature you'd need less often in the Group context.
Should there be a toolbar shortcut for the full-height option as there is in the Cover block? I'd learn towards no because it seems like a feature you'd need less often in the Group context.
Agreed.
👋🏼 Opened as many issues as I could from the list. A few notes on the items I didn't open issues for:
Comment navigation doesn’t have options for arrows like Next / Prev post and Post Navigation have.
Deleting a block with backspace seems to work only sporadically. Need to debug this.
The cover matrix alignment tends to mess up with width of the contents (align top, for example).
Could be nice to have a page number block as part of the navigation tools to display (with 1 being current)
Dragging stuff out of post template is generally very error prone and makes the blocks disappear at times. Pretty frustrating experience to lose content and being forced to undo, which also feels a bit buggy.
A note for an item I linked to a currently open issue:
It's frustrating to use the “query pagination” block.
Afaik, this is because the block doesn't inherit the query context when outside of the query loop. As a result, I linked to this issue but, depending on what you want, another issue might need to be opened: https://github.com/WordPress/gutenberg/issues/38684#issuecomment-1480124706I added the issues opened to the Phase 2 board for tracking with best guesses for priority and areas. Feel free to rearrange, edit the issues, etc.
Dragging stuff out of post template is generally very error prone and makes the blocks disappear at times. Pretty frustrating experience to lose content and being forced to undo, which also feels a bit buggy.
If it's what I think it is, I've been seeing this a lot, and would put a high emphasis on the importance of improving this. Here's a GIF showing dragging items in the list view:
So a few basic suggestions that don't preclude further improvements:
(For the comment navigation, the icon option is on the parent block, Comments Pagination, not the inner Comments Previous/ Next Page blocks.)
CC: @WordPress/gutenberg-design for visibility, there's a lot of good stuff here.
These are notes from @pablohoneyhoney and myself. I'll be turning them into separate issues.