We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For testing browsers, we shouldn't run the test until we get the load complete event. In Atspi this is "document:load-complete" (see orca code for handing from chrome: https://github.com/GNOME/orca/blob/34ba2393fc64c0e82f47da3900c7de398a89c2cb/src/orca/scripts/toolkits/Chromium/script.py#L168)
Until we do this, any test we write will be flaky.
The text was updated successfully, but these errors were encountered:
https://source.chromium.org/chromium/chromium/src/+/main:ui/accessibility/platform/inspect/ax_event_recorder_auralinux.cc;drc=5bf1a4a403490afa7294232e383a1750aefcc881;l=319
Sorry, something went wrong.
No branches or pull requests
For testing browsers, we shouldn't run the test until we get the load complete event. In Atspi this is "document:load-complete" (see orca code for handing from chrome: https://github.com/GNOME/orca/blob/34ba2393fc64c0e82f47da3900c7de398a89c2cb/src/orca/scripts/toolkits/Chromium/script.py#L168)
Until we do this, any test we write will be flaky.
The text was updated successfully, but these errors were encountered: