W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11068] We should not pause() if the element is removed from a document and then reinserted in the same task, since otherwise that could cause stuttering when moving a video from one frame to another, and would break autoplay when used with innerHTML.

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Jan 2011 01:35:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pg5uY-00075A-An@jessica.w3.org>

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-21 01:35:33 UTC ---
Use cases for this just looking at Google apps:

* drag-and-drop of a <video> or something containing a video should not pause
the video (e.g. imagine a widget in iGoogle that you can drag to elsewhere on
the page).

* popping out a video conference <video> from an in-page chat panel to a
separate window (e.g. imagine popping out a video conference happening in an IM
window in GMail).

* transitioning a video that is playing in a search results page into a video
that seems to be playing in a page dedicated to that video (e.g. imagine a
search on YouTube, where you can preview videos on the search page but once
you've picked one it dynamically reconstructs the page to be the main play page
for the video, using pushState and so on).

Obviously these use cases apply to more than just Google projects, I just
didn't want to pick on another company's products.

For autoplay="" and innerHTML, the problem is innerHTML is defined in terms
that involve a removal of the <video> node from a Document (a hypothetical one,
but that doesn't really matter), and that resets the autoplay functionality.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 21 January 2011 01:35:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:04 UTC