Allow regions to be locked

All the lock functions are working correctly. But the configuration icon is still showing when the block is locked. And the links are not clickable neither giving error messages which may confuse the end user.

Please see screenshot attached.

Wow, that's impressive, never thought about going that far as in locking regions :)

I'm checking the work to be done for D10 support, I'll probably start committing those things first, will come back after that to this one.

WOOOOOO, I've tested this, this is SO awesome :)

Current patch is partially broken because I've committed #3304761: Group lock settings in a details element, attached a new version to see what the test bot thinks.

Going to look at the code and tests a bit further now, this will definitely go in!

Ok, I don't have any remarks on the code or tests, they look great!

The only thing I wonder is whether the UI should make the feature a bit more clearer/explicit:

• Change title to something like: 'Lock block operations in following regions' ?
• Adding a description: 'Users won't be able to add, move, delete or add blocks in this region. This setting can also be applied in overridden layouts'. (this way #3244797: Allow new blocks in an overridden layout to be locked as well is covered completely).

This makes it a bit more clearer to me, because I can imagine people will come up with feature requests like 'But I want to only lock move or delete'. (even though I will point them to #3109715: Allow to add locks to components for that feature).

As English is not my native language, suggestions very welcome, after that, commit and release ! :)

If there are no remarks and all looks great then can we have this merged?

I think that having the same granularity with override locking as default locking might make for a more robust feature here.

What about sites where owners want lesser privileged users to be able to update overridden block content, but not rearrange them?

This is so awesome, and puts Layout Builder on closer parity with what WordPress can do with locking different parts of the Full Site Editor. I haven't tested this yet but will soon...

I've added the patch from @sonfd as a file here so it gets listed on top of the page

Changed title and added description for better user understanding.

I want to review latest MR ASAP and deploy it in the new 2.0.x branch.

After that, we can create some RC releases with the feature.

Okay, I finally configured the environment for the running of the tests.

I found that LayoutBuilderLockTest::testLock() fell because of the missing $blockId parameter in LayoutBuilderLockTest::checkBlockRouteAccess() method.

It looks like in Drupal 8/9 there was a way to fetch it via a magic method:

$blockId = $blockId ?? $this->body_field_block_uuid;

Going to investigate previous commits to the LayoutBuilderLockTest class, and maybe will find something related.

Okay, finally I've fixed all the tests. The problem was with the body_field_block_uuid property, which was renamed in previous commits, but not updated in each place of code.

In addition, there were new style issues with the readme file. Disabled cspell checks for the maintainer's section.

Rewritten javascript of the module. Instead of jQuery, I used pure JS and removed outdated dependency core/jquery.

Merged into 2.x, going to create RC.
Thanks, everyone for your contribution.