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

[Bug 12651] More things should set salvageable to false: XHR, plugins

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Aug 2011 04:17:18 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QtXZ8-0001pN-Pk@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
                 CC|                            |ian@hixie.ch
            Summary|More things should set      |More things should set
                   |salvageable. Like XHR. See  |salvageable to false: XHR,
                   |<http://trac.webkit.org/bro |plugins
                   |wser/trunk/Source/WebCore/h |
                   |istory/PageCache.cpp> for   |
                   |relevant code in safari     |
                   |(thanks ap)                 |

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-17 04:17:18 UTC ---
I assume you mean "more things should set salvageable _to false_".

I'm happy to add more things, or add hooks for other specs if necessary (I
think hooks already exist though).

The only case I could find from the source above that looked relevant is that
we can't bfcache a page if anything in its browsing context involves a live

The other things didn't look like things we should add to the spec, though. For
example, why would the use of shared workers affect it? Why would encrypted
pages be affected?

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 Wednesday, 17 August 2011 04:17:20 UTC

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