anon99583818:
are columsn to be deprecated? i see some major bugs in here and never heard of a roadmap for this
For some basic use by clients/editors they are probably fine, although they have known limitations (like not being able to delete/add blocks directly from the navigator, etc).
For templating and developer use, they are mostly redundant now that we have Grid layout on any block.
anon99583818:
the UX navigatior module…this must work more stable and precise…i personally can not work with this…layers at least some must be choosable at once and those mouse bugs and inserting speed must be enhanced, we dont have time to struggle with that essiential one
From my view there are only two things that are must haves for this:
Fix the drag preview positioning:
Description:
When dragging a block to move it in the Navigator, the dragged block does not always keep up with the movement of the cursor/drag preview box. The expected behaviour is that it will “stick” to the cursor more. This seems to happen when the cursor initially moves quickly upwards causing the block to be shifted inside/outside of a containing block. When this happens, the delta remains at this extended distance and does not snap back to the cursor for the duration of the drag.
Screen…
Add support for multiple selection:
Just throwing this one with complete patience and understanding.
I think the drag/drop may be very complex to do as we’re dealing with wrappers and possibly the reason why the shift click was not introduced.
If it is a potential easy implementation, then why not the shift click as a starter? After woocommerce I mean
Other than that I don’t see any stability issues.
anon99583818:
parameters which are not able to combine must produce an UX error message / hint…now its more try and error usability…no time for this in complex projects
Which parameters are you referring to?