Repair wp/6.7 branch Actions: Improve reliability of TinyMCE-related tests - #82905

Part of #82783.

What?

Two fixes to test/e2e/specs/editor/plugins/wp-editor-meta-box.spec.js, the WP Editor Meta Boxes spec:

1. Clicks the mode-switch button by the name it actually has on this branch, Text, instead of Code.
2. Replaces the test's iframe-presence wait with a wait on TinyMCE's own initialized flag, and adds the same wait after switching back to Visual mode.

No change to what the test asserts.

Why?

The wrong selector

The test was consistently failing (not intermittently) on wp/6.7, timing out on a click of role=button[name="Code"i]. That button does not exist in this branch's bundled WordPress: its wp-env config pins WordPress Core to WordPress/WordPress#6.7-branch, which still renders the classic-editor tab as Text (wp-includes/class-wp-editor.php). Core renamed that string to Code after 6.7-branch was cut — it shipped in WordPress 6.8 — and Gutenberg trunk followed suit in #68872/#68886. That rename does not apply here, because this branch's wp-env is deliberately pinned to match its own WordPress version (#82900, lower in this stack). A hardcoded wrong locator fails every time, which is exactly what CI showed.

So this branch clicks Text.

The initialization wait

Separately, the test guarded its mode switch with:

await page.locator( '#test_tinymce_id_ifr' ).waitFor();

That waits for the editor iframe element to be attached, which happens early in TinyMCE's startup — not at the end of it. The comment above it already claimed the intent was to wait "for it to initialize"; this makes the code actually do that.

When the mode switch lands inside that window, two things can go wrong: TinyMCE flips the editor back to Visual once initialization completes, discarding the typed text, and getSelection() can return null while TinyMCE restores the cursor position. Both surface as intermittent failures in end2end-test.yml.

Waiting on window.tinyMCE.get( 'test_tinymce_id' ).initialized closes the window, because that flag is set only after startup finishes. The bundled TinyMCE is 4.9.11 on every WordPress version these branches pin, and it defines window.tinyMCE, returns the instance from EditorManager.get( id ), and sets .initialized on it.

This part is a straight port of 631bcb2 (#78631) from trunk, except for the branch-specific button name.

Trunk's current version of this test also clicks a "Meta Boxes" pane-toggle button, added by #71623. That toggle only renders under a narrow-height media query this branch's CI viewport doesn't trigger, so porting that unrelated UI feature to a frozen maintenance branch is out of scope here.

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