Set Ready For Review
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I'm afraid I cannot view the bug or the videos due to access restriction.
Having said that, did you also test to be sure that legitimate text edits and selection changes continue to be reported, such as arrowing left/right, selecting/unselecting text via keyboard navigation, using backspace/delete, typing new values, etc.?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// If the node is an <input type="number"> (identified as a spin button) andI haven't dug into the history of when the surrounding code landed, but
// TODO(nektar) Remove this once editing intents are implemented,
// and the actual inserted and deleted text is passed over from Blink.
is really the right way to do this.
Many editing intents did land (see
u/a/mojom/ax_event_intent.mojom
u/a/ax_enums.mojom
).
We should be able to do a bit better e.g. detect value or selection changes based on typing vs insertions by Blink. I don't think we pass over the inserted, deleted text though, but should at least be able to know if the text was inserted/deleted as opposed to typed.
Removing myself from reviewer, David has it covered :)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |