Skip to content

test(e2e): keep annotation input ordered and wait for view bounds to settle - #459

Merged
bubbleptr merged 1 commit into
mainfrom
fix/annotation-e2e-input-order
Oct 10, 2026
Merged

bubbleptr merged 1 commit into
mainfrom
fix/annotation-e2e-input-order

Conversation

@bubbleptr

@bubbleptr bubbleptr commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • The v0.3.0 Release failed twice at the packaged-app E2E: Annotate mode marks a strict-CSP page… never saw 1 comment. Instrumented CI runs showed the Enter keydown reached the overlay with every guard passing, but saveEditor read an empty textarea: webContents.insertText and sendInputEvent travel on different channels, so on the CI runner Enter could be handled before the text landed. The helper now types each character as a char input event, which shares Enter's path and stays ordered.
  • Browser surface loads a page… read the native view width once after a resize and could catch it mid-sync (576 vs 636 on CI). It now polls until the view matches the placeholder within 1px.
  • Test-only change; no app code touched.

Test plan


Devin Review

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@bubbleptr
bubbleptr merged commit 727417b into main Oct 10, 2026
3 checks passed
@bubbleptr
bubbleptr deleted the fix/annotation-e2e-input-order branch October 10, 2026 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant