Status: Assigned Owner: [email protected] Labels: Type-Bug Pri-1 OS-All Area-BrowserBackend Size-Medium Mstone-3 Video
New issue 18975 by [email protected]: Implement networkState and readyState more accurately http://code.google.com/p/chromium/issues/detail?id=18975 Higher priority than our default UI since it effects all UIs built on top of our API. For starters, our networkState will rarely be LOADED (perhaps if it's file:// otherwise we're continuously LOADING). Our readyState should reflect how much we can play at this very moment. What this means is a seek should drop our readyState to HAVE_METADATA. When the seek completes we can raise the value back to HAVE_ENOUGH_DATA. WebKit should pick up on our cues and fire the corresponding events (waiting, seeking, etc..) The initial load might be a little tricky... it'd be nice if we can jump to LOADING right away (which is true) and HAVE_METADATA as soon as possible (so the element can report its size accurately and the page will continue laying out). CURRENT EVENT OUTPUT: playing timeupdate timeupdate ... (seek somewhere) (time passes, timeupdate stops firing) seeked timeupdate timeupdate ... EXPECTED EVENT OUTPUT: playing timeupdate timeupdate ... (seek somewhere) waiting (according to spec, this comes before seeking) seeking (time passes, timeupdate stops firing) seeked timeupdate timeupdate ... There's also the issue of firing progress events, but that's a separate issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
