New issue
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
Implement missing ready states transition #31706
base: main
Are you sure you want to change the base?
Conversation
I tested the changes locally and they seem to be going in a great direction. It fixes the problem I was having in #31416 (comment) with the |
645a5b5
to
191d485
Compare
🔨 Triggering try run (#8754867367) for Linux WPT |
Test results for linux-wpt-layout-2013 from try job (#8754867367): Flaky unexpected result (21)
Stable unexpected results that are known to be intermittent (15)
Stable unexpected results (12)
|
Test results for linux-wpt-layout-2020 from try job (#8754867367): Flaky unexpected result (23)
Stable unexpected results that are known to be intermittent (19)
Stable unexpected results (10)
|
|
Implementation is still pretty crude (panics if `idx` is out of bounds). It's good enough for prototyping though. I will improve it once I get things working.
Fixes CRASH /html/semantics/embedded-content/the-video-element/resize-during-playback.html
To narrow down the source for TIMEOUTs, I want to know which events are queued.
Strictly speaking for `PlaybackState::Playing` the ready state could be any of * `ReadyState::HaveCurrentData` * `ReadyState::HaveFutureData` * `ReadyState::HaveEnoughData` if the previous ready state was at least `ReadyState::HaveMetadata`. We already assume the best case (i.e. `ReadyState::HaveEnoughData`) for `PlaybackState::Paused` and we are fixing another unexpected WPT test result (namely `/css/selectors/media/media-playback-state.html`) by doing the same for `PlaybackState::Playing`.
./mach build -d
does not report any errors./mach test-tidy
does not report any errors