In a recent update, Bricks introduced an automatic rename mode every time you select an element in the structure panel. This goes against basic UX principles. Selecting should simply select — not instantly trigger editing state. The cursor blinking automatically is also visually distracting. On top of that, this creates a risk of unwanted/accidental renames.
We already had a double-click rename action that was easy and predictable, so this new behavior is really unnecessary.
Can we please revert this change or at least make it optional in the settings?
Well I get the Cursor in Insert mode. Its pretty hard to even spot to be honest.
Its not in rename.
If I double click an element then the text ( element name ) is highlighted and anything you type then replaces the previous. I assume that’s what you mean?
Renaming elements should only be possible with a double-click, like it was before. If you now single-click an element in the structure panel, you can start typing right away, which is not ok.
Thanks for this request, I already wanted to write this too.
Also copy and paste of elements needs to work with CTRL/CMD+ C/V. Guess how many times I‘ve pasted encoded element text into the name field in the last week
I agree with the request to revert the single click on an element back to select rather than edit. Or please provide a Bricks setting to choose which function to perform on element single click. Working in Bricks has become more fragile. It is a less common UI approach. Much of this has been discussed in Facebook posts (I understand the Bricks team does not officially monitor Facebook). Even Sridhar agrees ! That must carry extra weight ….
Not to sound negative, but I can tell you right away this is not the optimal solution. Clicking anywhere on the element in the structure panel should simply select the element, like you select a file in a file browser on any OS. Rename should only be initiated with a double-click, or a special action (context menu, icon etc.).
Please let us know if you are still experiencing issues.
As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment. The more feedback we get, the better