Block Grid components are not fully clickable in Umbraco 14

[petervangennip]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.1

Bug summary

In Umbraco 14, when using the Block Grid, only the small edit button or pencil icon within each block is clickable to access the editing interface. The entire block area should be clickable, as this limited clickable area restricts ease of use and productivity for content editors. Expanding the clickable area to the whole block would improve the editing workflow and make the interface more intuitive.

Specifics

Umbraco Version: 14
Affected Area: Block Grid editor in the Umbraco backoffice
Browser: All supported browsers
Component: Block Grid editor (UI/UX issue)

Steps to reproduce

1. Open an Umbraco 14 project with content in the Block Grid editor.
2. Navigate to a Block Grid editor instance containing one or more blocks.
3. Attempt to click on the body of a block (outside of the edit button/pencil icon) to open the edit interface.

Expected result / actual result

Expected Result
Clicking anywhere within a Block Grid component should open the editing interface for that block. This provides an intuitive and faster editing experience, allowing content editors to click directly on any part of the block.

Actual Result
Only the small edit button or pencil icon within each block is clickable. Clicking outside of this icon, within the block, does not open the editing interface, which limits the user experience.

[github-actions]

Hi there @petervangennip!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂