fix: replace and verify native fill values (TKT-996) - #2756
Merged
Merged
Conversation
Contributor
✅ Tests passed: 3074/3077Ran 16 of 16 suites (0 not affected by this change).
|
Nikhil (shadowfax92)
marked this pull request as ready for review
September 24, 2026 02:48
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes TKT-996: filling a prepopulated field could append, and non-editable fields could report success without changing.
Both surfaces share the Rust operation. Trusted input events reach page handlers; unreadable/detached fields cannot be mistaken for empty. Existing matching values are idempotent success. Search readiness and login outcomes require application-specific checks.
Evidence
After: replacement, rejected edits, controlled rollback, empty clearing, native events, shadow/cross-site frame focus and explicit append have browser contracts on both surfaces.
bun run checkandbun run testpassed; existing lint/Fallow warnings remain.xboxis set, trusted input fires, and Search enables after its widget debounce.The suite's fixture inventory and an existing stopped-session error assertion were updated to match the actual fixture set and server response.
All checks passed on
0d1c2c935. Linux CI now uses the suite's headless default. Its former Xvfb requirement was for retired hidden-window APIs; the full native-input suite remains enabled.Merge Danger
Door: two-way; code revert, no schema or data migration.
Blast Radius: MCP fill through act and run. Unsupported controls, rejected/normalized values and wrong focus now produce errors. Fill emits native text-input events; use type/press when keyboard handlers are required.