InputMsgWatcher input_watcher(rwh, blink::WebInputEvent::Type::kKeyUp);Doesn't tab key down trigger focus change?
shell()->web_contents(), ui::AXEventGenerator::Event::FOCUS_CHANGED);If we're simply concerned with a11y focus, then it seems like busy while waiting for focus node to match the target name should suffice.
As is, it's I guess possible we end up matching against the wrong focus event since we're tabbing potentially more than once.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
InputMsgWatcher input_watcher(rwh, blink::WebInputEvent::Type::kKeyUp);Doesn't tab key down trigger focus change?
Sometimes more than once. As per the other comment though, you're right that this same thing is achievable without the InputMsgWatcher. Cleaned this up.
shell()->web_contents(), ui::AXEventGenerator::Event::FOCUS_CHANGED);If we're simply concerned with a11y focus, then it seems like busy while waiting for focus node to match the target name should suffice.
As is, it's I guess possible we end up matching against the wrong focus event since we're tabbing potentially more than once.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |