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: PaulREnglish <bbpaule@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

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

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @PaulREnglish! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

Good catch, @PaulREnglish!

I can confirm the bug; however, the proposed fix doesn't exactly resolve the issue. If we change the arguments for Array.some, the edit will become index, which is usually the second argument for similar array callbacks.

What that condition is trying to check is whether any edit is different from the original post object. I think the problem here is that someone accidentally used Object.values instead of Object.entries. Switching to the latter should fix the error and the check.

This is probably a regression after #35929.

diff --git a/packages/editor/src/store/actions.js b/packages/editor/src/store/actions.js
index 81b96e827c..829976b7c1 100644
--- a/packages/editor/src/store/actions.js
+++ b/packages/editor/src/store/actions.js
@@ -62,7 +62,7 @@ export const setupEditor =
 		}
 		if (
 			edits &&
-			Object.values( edits ).some(
+			Object.entries( edits ).some(
 				( [ key, edit ] ) =>
 					edit !== ( post[ key ]?.raw ?? post[ key ] )
 			)

Good catch, @PaulREnglish!

I can confirm the bug; however, the proposed fix doesn't exactly resolve the issue. If we change the arguments for Array.some, the edit will become index, which is usually the second argument for similar array callbacks.

What that condition is trying to check is whether any edit is different from the original post object. I think the problem here is that someone accidentally used Object.values instead of Object.entries. Switching to the latter should fix the error and the check.

This is probably a regression after #35929.

diff --git a/packages/editor/src/store/actions.js b/packages/editor/src/store/actions.js
index 81b96e827c..829976b7c1 100644
--- a/packages/editor/src/store/actions.js
+++ b/packages/editor/src/store/actions.js
@@ -62,7 +62,7 @@ export const setupEditor =
 		}
 		if (
 			edits &&
-			Object.values( edits ).some(
+			Object.entries( edits ).some(
 				( [ key, edit ] ) =>
 					edit !== ( post[ key ]?.raw ?? post[ key ] )
 			)

Thanks for taking a look and the detailed explanation!

I've reverted my original proposed fix and implemented the Object.entries change.