-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use nested blocks for quotes #6520
Conversation
blocks/rich-text/style.scss
Outdated
@@ -82,7 +82,7 @@ | |||
|
|||
.block-rich-text__inline-toolbar { | |||
display: flex; | |||
justify-content: center; | |||
justify-content: attr( data-justify-content ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasmussen I don't know if this is a good way to address the issue where the toolbar should be aligned the same as the content? Looking at the text-align
property seems too hard to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit hard to grok for me without a screenshot. I'm also not familiar with the justify-content
property. Is this about the alignment of the inline toolbar in context of that text being non-centered?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasmussen Sorry, I changed it in the meantime because this didn't work... I've added the styles inline in React now. Ideally the toolbar should be positioned the same as the text, but it doesn't seem like there's an easier way to do it. The block has to set the toolbar position as well.
fee5758
to
56315f1
Compare
There are a lot of conflicts with this branch, I'm guessing because it's a bit old. Could you rebase onto master before we get to reviewing, just in case the conflict resolution changes anything non-trivial? |
Rebasing... |
56315f1
to
797b221
Compare
Oh, it's again out of date. Migrations stopped working for some reason, looking into it, and fixing e2e tests. |
2555cc3
to
39c7a79
Compare
Once more out of date :) |
39c7a79
to
b49cef0
Compare
Discovered by an e2e test (yay): The in-between inserter is odd at the edges of a nested block areas. It's not clear where the block should be inserted: above the wrapper or inside the wrapper. For users this will get a bit confusing. Cc @jasmussen @karmatosed. |
b49cef0
to
2dcba4d
Compare
This is the new version, correct? Can you elaborate a bit on this? Is it a visual issue or a technical one? |
Yes, current master.
Visual/UX. There are two possible insertion points at one single line at the edges of nested block areas. |
2dcba4d
to
d9ad0d5
Compare
d9ad0d5
to
cc659d6
Compare
@iseulde @jasmussen The Divi Visual Builder gets around this issue by shifting the inserter buttons to the left or right when they get too close together and by having different colors for the inserter buttons depending on whether something is a section, row, or module. Not exactly sure how something like this would be implemented in Gutenberg, but I thought I would point it out anyway in case it gives any ideas: |
@iseulde @jasmussen The sibling inserter issue could be resolved if something like these mockups I made in #6224 was implemented. This would make it very clear where a block would be inserted, since the sibling inserter would be more closely tied to the block it is inserting after. There would also be no overlapping sibling inserters like there are now. |
Because #6054 was merged, I'm going to close this. It looks like this should've been closed but it slipped through the cracks. |
@tofumatt That commit was reverted. |
Shoot, I see, my bad 😓 Sorry, I was just trying to clear up old PRs still flagged for review. Does this still require a review then? |
I think this just needs another rebase, but it seems less important atm. |
Fair enough, sorry I was working backward through my review queue so no rush 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one needs a solid rebase to bring it up to date. @youknowriad - is this something we want to spend time on in Phase 2? Does it make sense to refresh it or should we rather close it and reopen in the future when it's necessary? I'm marking it as Stale until it will get revisited.
I'm pointed here through this ticket: https://core.trac.wordpress.org/ticket/46341 Any chance to go ahead with this issue? For me it looks like it's stil open but no work on it. (I'm a newbee here on github, so please excuse if I missunderstand this thread.) |
@Sven74Muc Yes, this pull request (branch) should be rebased or we could also start from scratch. Last time I checked the code looked good, but there were some issues with the design of nested blocks that made us want to wait with this until they are resolved. I'm not sure if this is still the case. Cc @jasmussen or @karmatosed? Do you think we can move forward with using nested blocks in the quote blocks? |
@iseulde For me it is not only about nested a bullet list within quote. There are also other blocks like table or column which could be nested in a quot. On the other side ther could also be a bullet list nested in a table or column for example. So.... column for example (or other) could be nested somewhere else or other way arround other things could be nested within column (or other) "using nested block in a quote block" AND nest a quote block in other blocks like table. Think it makes sense not just to go for one case, it should be an in all directions flexible solution. What do you think? |
@jasmussen @karmatosed @iseulde For me it looks with the bigger appraoch (not just nested blocks within quotes) that it makes sens to start from scratch. Maybe one approach ist like with the header block... there you have the align functionality within the right sitebar... So not a nested approach, more a seperated approch. |
@ellatrix should we then close this and redo the whole thing? By the looks of the conflict list it would be a horror story to rebase :D |
Sure :) |
Revert "Revert "Use nested blocks for quotes (#6054)" (#6501)"
This reverts commit 230ad0d.
Description
Redo of #6054.
Things to fix:
Formatting toolbar for cite.Cite placeholder is hard to discover.There should be no arrows if there is only one block.How has this been tested?
Create a quote and pull quote block.
Checklist: