Fixed flaky post publish browser tests

[kevinansfield]

no issue

• we're seeing flaky browser tests when publishing posts where we can navigate away from the admin area to check for a published post before the publishing PUT request completes, causing an aborted request and a 404 for the post that never got published
• added a wait for the "success" state of the save, indicated by the publish button no longer being visible so we're not navigating away to the frontend before the save request has completed

[coderabbitai]

Walkthrough

This change modifies an end-to-end browser test by replacing a placeholder comment with actual wait logic. After clicking the publish confirmation button, the test now explicitly waits for the confirm-publish button to become hidden before proceeding, ensuring the publish workflow completes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a wait condition to fix flaky post publish browser tests by ensuring the publish request completes before navigation.
Description check	✅ Passed	The description clearly explains the root cause of the flaky tests, the specific problem, and the solution implemented, all directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}