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

Re: PeerConnection and the bfcache

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 29 Nov 2011 06:02:26 +0100
Message-ID: <4ED46762.1050807@alvestrand.no>
To: Ian Hickson <ian@hixie.ch>
CC: public-webrtc@w3.org
On 11/28/2011 10:49 PM, Ian Hickson wrote:
> 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.
Thanks very much for the heads-up!

The editors will do this together with some other cleanup to align with 
current practice.
Received on Tuesday, 29 November 2011 05:02:57 UTC

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