e2e: editor-docs '(reference — F1)' completion-link test fails consistently on Firefox (regression from #320, reddens main)

[BorisTyshkevich]

Summary

tests/e2e/editor-docs.spec.js:100 — [firefox] › docs reference (#313) › completion info exposes the "(reference — F1)" link that opens the same pane — fails consistently on Firefox (chromium + webkit pass) on main. Confirmed reproducible: two consecutive runs of the same commit both fail on this one test (215 passed, 1 failed each time), so it is not a transient flake.

• Failing run (main 8f746d2, the Version-exact ClickHouse reference documentation in Workbench #60/feat(#60): version-exact ClickHouse reference docs — CM6 hover/F1, non-modal pane, structured sources, system.documentation Markdown #320 merge): https://github.com/Altinity/altinity-sql-browser/actions/runs/29719619592
• Prior main commit 5925ef6 was green — the regression landed with PR feat(#60): version-exact ClickHouse reference docs — CM6 hover/F1, non-modal pane, structured sources, system.documentation Markdown #320 (Version-exact ClickHouse reference documentation in Workbench #60 docs reference).

Symptom

[firefox] editor-docs.spec.js:100 › completion info exposes the "(reference — F1)" link…
  Error: locator.click: Test timeout of 30000ms exceeded.
  107 |  expect(await btn.evaluate((el) => el.tagName)).toBe('A');
  108 |  await expect(btn).toHaveText('reference');

The .click() on the completion-info "reference" link never resolves on Firefox — the link/tooltip likely isn't present or interactable at click time.

Likely cause

The documented CM6 completion-popup race (see maintainer memory cm6-completion-race-in-e2e): the completion popup + its info tooltip open ~100ms after typing, and Firefox's timing differs from Chromium/WebKit. The test appears to type to open completion then click the info link before Firefox has rendered it. Fix direction: drive the doc/selection via view.dispatch and explicitly wait for the completion info tooltip (.cm-completionInfo / the reference link) before clicking, rather than relying on post-type timing.

Why deferred

Out of scope for #321 (Grid Tiles / Full view — a Dashboard change touching none of the editor/docs/completion path). Filing separately per the working-discipline rule rather than folding a #313 test fix into the #321 PR. Note this currently reddens main's e2e and therefore every branch's e2e, so it blocks merges until fixed.