W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2011

PeerConnection and the bfcache

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 28 Nov 2011 21:49:53 +0000 (UTC)
To: public-webrtc@w3.org
Message-ID: <Pine.LNX.4.64.1111282124390.2514@ps20323.dreamhostps.com>

As part of removing the PeerConnection interface from the WHATWG spec, I 
also removed this paragraph which was not included in the webrtc.html 
file from which this WG's spec was forked:

-   <li>
-
-    <p>If the <code>Document</code>'s <code>Window</code> object <span
-    title="concept-PeerConnection-owner">owns</span> any
-    <code>PeerConnection</code> objects whose
-    <span><code>PeerConnection</code> readiness state</span> is not
-    <code title="dom-PeerConnection-CLOSED">CLOSED</code>, then set
-    <code>Document</code>'s <var
-    title="concept-document-salvageable">salvageable</var> state to
-    false.</p>
-
-   </li>

This was part of the unloading document cleanup steps:
http://www.whatwg.org/specs/web-apps/current-work/#unloading-document-cleanup-steps

The WebRTC spec should define an unloading document cleanup step that 
consists of something equivalent to the above to avoid having documents 
with open PeerConnection objects survive in the bfcache.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 28 November 2011 21:50:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:26 UTC