mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-22 01:35:35 +00:00
a410e8138e
Since the media element is playing directly after play(), not waiting for the readyState to advance before play()ing could leave the play promise from play() unhandled until cleanup, when it would be rejected by the load algorithm. This would happen if a timeupdate event is raised before the first frame comes in to update the readyState, which resolves the play promise. Waiting for the readyState to advance before play()ing seems like the cleanest fix wrt testing currentTime after the first timeupdate event. Depends on D33655 Differential Revision: https://phabricator.services.mozilla.com/D34686 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| awsy | ||
| config | ||
| crashtest | ||
| extensions | ||
| firefox-ui | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webdriver | ||
| xpcshell | ||
| addtest.py | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| parse_build_tests_ccov.py | ||
| README.txt | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testsuite-targets.mk | ||
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff