Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
If we're to remove this, the corresponding entry should also be removed from the
editor/assets/stylesheets/_z-index.scss
file.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.
@aduth That sounds like a good idea, and I think that at least lowering the z-index for the corresponding SASS style sheet would probably be the safer, less invasive alternative, since removing this line here ultimately would have the same effect of reducing the z-index in the corresponding SASS style sheet, just a much more lowering effect.
Forgive me if this is the wrong place to ask this, but while I have your attention on this issue, I'd like to ask a bigger question:
What is the plan for introducing the drag and drop ability for the blocks to re-order and position themselves by dragging them around, and perhaps add new blocks by dragging them in from a list of available block choices?
For a form-based editor WP plugin that I am building for a client, so that users can build forms by dragging around form elements and add in new form elements by dragging them in to the main form 'tree', I've worked considerably with react-sortable-tree, even creating the feature myself for giving its API the ability to drag in new external nodes, from this merged PR. React-sortable-tree's dragging ability is built solely on its bedrock of React-dnd.
I've enjoyed the abstracted, focus-on-the-data-not-the-DOM approach of React Dnd, and I am curious what you think of the possible application of React Dnd (or possibly even react-sortable-tree) is for Gutenberg.
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.
There's a few related issues at #38 and #1511
My understanding is the general sentiment is that drag-and-drop is not a goal for primary block arrangement, but could be added as an enhancement on top of current arrangement tools. Drag-and-drop is tough to get right, and particularly so for long-content posts.
I don't have much personal experience with the two options you raised, aside from general awareness of their existing. I did have a hand in implementing a similar component in Calypso which could similar apply or inspire for a similar behavior in Gutenberg.
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.
Thanks for the response! I think the drag and drop ability for blocks within Gutenberg is definitely worth pursuing, and consensus in the community surrounding this, ultimately architectural, issue would be great, so the direction for accomplishing this could be seen as consistent and uniform. Just my two cents.