The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: up1512001 <up1512001@git.wordpress.org>
Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: richtabor <richtabor@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Similar to the other PR. Is there a way to solve this without having the knowledge of the block editing mode within the block itself? (See question here #65699 (comment) and reply)

Is there a way to solve this without having the knowledge of the block editing mode within the block itself?

So rather passed to the block somehow?

Block editing mode has been used in the image block since its creation, and in the meantime is used in more places than just navigation and image:

grep -rl 'useBlockEditingMode()' ./packages/block-library/src
./packages/block-library/src/paragraph/edit.js
./packages/block-library/src/heading/edit.js
./packages/block-library/src/navigation/edit/index.js
./packages/block-library/src/template-part/edit/inner-blocks.js
./packages/block-library/src/image/edit.js
./packages/block-library/src/button/edit.js
./packages/block-library/src/post-featured-image/edit.js
./packages/block-library/src/media-text/edit.js
./packages/block-library/src/post-title/edit.js
./packages/block-library/src/cover/edit/index.js

And there are three states: 'disabled', 'contentOnly', and 'default' so blocks might need to behave differently according to the value.

What if it were passed down through useBlockProps?

diff --git a/packages/block-editor/src/components/block-list/use-block-props/index.js b/packages/block-editor/src/components/block-list/use-block-props/index.js
index 25b9a21f0d..b30d9889e5 100644
--- a/packages/block-editor/src/components/block-list/use-block-props/index.js
+++ b/packages/block-editor/src/components/block-list/use-block-props/index.js
@@ -161,6 +161,7 @@ export function useBlockProps( props = {}, { __unstableIsHtml } = {} ) {
 		'data-block': clientId,
 		'data-type': name,
 		'data-title': blockTitle,
+		'data-editing-mode': blockEditingMode,
 		inert: isSubtreeDisabled ? 'true' : undefined,
 		className: clsx(
 			'block-editor-block-list__block',

It's a good discussion to have! Is it a blocker for this PR though?

If a better way to communicate block editing mode to blocks comes along, migrating affected blocks in the block library will have to be done anyway.

You're right, it doesn't seem like a blocker for the current PR.

@t-hamano addressed your feedback, please check now.

I'm not sure when it happened, but I noted that this has been resolved. #66875 (comment)