Playwright Firefox-with-plugins: 4 specs fail with non-keystroke root causes after #7622

[JohnMcLear]

After #7622 began discovering plugin Playwright specs, the Playwright Firefox with plugins CI job has multiple failing tests beyond the keystroke-drop class addressed by #7625.

Each looks independent and likely needs a per-spec fix in the owning plugin or core repo.

Failing specs

Reproducible on develop HEAD, no special steps beyond running the standard pnpm test-ui --project=firefox with WITH_PLUGINS=1.

Spec	Test	Symptom
plugin_packages/.versions/ep_headings2@0.2.112/.../headings.spec.ts:44	Option select is changed when heading is changed	21s expect timeout
plugin_packages/.versions/ep_markdown@11.0.17/.../markdown.spec.ts:10	Bold section renders the markdown class on body when "Show Markdown" is enabled	90s test timeout
plugin_packages/.versions/ep_spellcheck@0.0.92/.../spellcheck.spec.ts:9	Spellcheck is on by default when not disabled	90s test timeout
tests/frontend-new/specs/timeslider_identity_changeset.spec.ts:16	timeslider playback advances through all revisions including identity changesets	90s test timeout

What's already addressed

• ep_align, ep_font_size, ep_table_of_contents, ep_author_hover — fixed in their respective plugin repos and republished.
• The general keyboard.type → insertText Firefox flake — test(playwright): use insertText so Firefox stops dropping keystrokes #7625.

Likely causes (unconfirmed)

These look like the same family of bugs the ep_align spec had: assertions on the wrong DOM element, missing force: true on a click that the #toolbar-overlay intercepts, or selectors that resolve to a render that hasn't happened yet. Each needs a 5-10 minute investigation against a local Etherpad with WITH_PLUGINS=1 (Firefox).

These don't block #7624 — they exist on develop independently. Filing here so they get fixed against the right plugin repos rather than accumulating in unrelated PRs.

[JohnMcLear]

Could this have been caused by the ep_author_trace bug that we discovered and not actually a real bug? Best to check, this might be a non-bug now..