Repository navigation
Repair wp/6.8 branch Actions: Reset preferences after navigable toolbar e2e tests - #83723
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Size Change: 0 B Total Size: 1.85 MB ℹ️ View Unchanged
|
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
7acbb91 to
7628d80
Compare
7628d80 to
d40462d
Compare
d40462d to
bb0e030
Compare
bb0e030 to
6bdbd93
Compare
6bdbd93 to
bf56468
Compare
bf56468 to
a56d1cc
Compare
Part of #82786.
What?
Resets preferences through the REST API after every test in
test/e2e/specs/editor/various/navigable-toolbar.spec.js, instead of turning the fixed ("Top") toolbar back off at the end of two of its tests.Why?
The "Block toolbar will scroll to reveal hidden buttons with fixed toolbar" test turns the fixed toolbar on and, as its last step, off again. Preferences are saved to the server with a 2.5-second debounce, so when the test finishes quickly the page closes before the "off" is saved, and the server keeps
fixedToolbar: true. Every later post-editor test in the same shard then loads with the top toolbar on: the floating block toolbar and the editor top bar's "Back"/"Options" buttons aren't where those tests expect them, so they fail on every retry. This branch has the same test and the same debounced preference saving, so the fix is included for consistency.requestUtils.resetPreferences()writes the preferences directly over REST from the test runner, so it doesn't depend on the page staying open, and it also runs after a failed test.Upstream
A straight cherry-pick of
2e877e9(#78115) fromtrunk.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.
🤖 Generated with Claude Code