New issue
Advanced search Search tips

Issue 603973 link

Starred by 3 users
Status: Available
Owner: ----
Cc:
sande...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

WMPI should not rely on the ordering of OnBufferingStateChanged()

Project Member Reported by sande...@chromium.org, Apr 15 2016 
WMPI currently drops OnBufferingStateChanged() callbacks if they happen during a seek or suspend/resume operation, on the assumption that any such event is from before the operation started.

While this is true, it is an invariant that spans multiple classes, is easy to break, and is not documented in any interface. The requirement should be removed, likely by associating the callbacks with a generation counter (or equivalent mechanism).
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 17 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by sande...@chromium.org, Apr 19 2017

Status: Available (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 20 2018

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by dalecur...@chromium.org, Apr 20 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment