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

[Bug 12227] The readyState check in the "potentially playing" definition should not be used to influence GC of media elements

From: <bugzilla@jessica.w3.org>
Date: Thu, 03 Mar 2011 06:34:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pv27P-0005sj-Q2@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12227

Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |philipj@opera.com

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-03-03 06:34:35 UTC ---
(In reply to comment #0)
> The problem with this is that there is still a race between the GC and the
> network in this example:
> 
> function playAudio() {
>   var a = new Audio("http://www.example.com/music");
>   a.play();
> }
> 
> This means that after the function exits, the behaviour will vary depending
> upon whether the GC fires before or after readyState gets to HAVE_FUTURE_DATA.

After the function exists, paused will be false, so it will be "potentially
playing". I think what you mean is that it could be GC'd just before a.play().

Another example where I'm unsure of the behavior is:

var a = new Audio("http://www.example.com/music");
a.canplaythrough = function() { a.play(); };

-- 
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 Thursday, 3 March 2011 06:34:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 March 2011 06:34:39 GMT