Before bfcache we have the invariant that the prescontext's link handler and container are both the same -- the docshell. With bfcache, we null out the link handler but not the container in cached presentations. We should sort our exactly what these do and figure out whether we should be nulling both, neither, or only one and why, then document it. I also think we should just nuke both members and use the document's container, but that may confuse printing....

Comment on attachment 186773 [details] [diff] [review] null out the prescontext container r+sr=dbaron, assuming it doesn't need to be re-set elsewhere :-)

Comment on attachment 186773 [details] [diff] [review] null out the prescontext container Requesting approval; only impacts fastback.

Comment on attachment 186773 [details] [diff] [review] null out the prescontext container a=me for 1.8b3. /be

checked in

I'd still like to see some documentation on what these members are and why just nulling out both makes sense (in particular why no one ever assumes they're non-null, which they generally are in normal browsing).