Kris Maglione 1722817403 Bug 1582832: Part 1 - Make FrameLoader owner rather than DocShell responsible for discarding a BC. r=nika ... There are all sorts of lifecycle issues which arise from making DocShell responsible for discarding BrowsingContexts. In this particular bug, we tend to run into them in cases where we create a BrowsingContext for a FrameLoader, and then never create a DocShell for it, leading to it never being destroyed. But there are myriad other issues as well. This patch moves the responsibility for BrowsingContext lifecycle management to the FrameLoader/FrameLoaderOwner, rather than the DocShell, which makes things more consistent, and more closely aligns with spec-defined behavior. Differential Revision: https://phabricator.services.mozilla.com/D59008 --HG-- extra : moz-landing-system : lando		2020-02-06 19:07:56 +00:00
..
base	Bug 1582832: Part 1 - Make FrameLoader owner rather than DocShell responsible for discarding a BC. r=nika	2020-02-06 19:07:56 +00:00
build	Bug 1574372 - Allow using nsWebNavigationInfo statically. r=bzbarsky	2019-12-17 03:01:37 +00:00
resources/content	Bug 1562642 - add missing license in docshell/resources/content/netError.js r=smaug	2019-11-12 08:26:18 +00:00
shistory	Bug 1600254 - P8: Make nsIInputChannelThrottleQueue work with socket process r=dragana	2020-01-30 13:32:55 +00:00
test	Bug 1611469 - backgroundPageThumbsContent.js mixes nsIRequest and nsIWebNavigation load flags r=markh	2020-01-28 14:47:23 +00:00
moz.build	Bug 1594981 - update Core::DOM* and Core::Storage* bugzilla product and component meta data in moz.build files after reorganization in bug 1594717. r=annevk	2019-11-08 12:17:57 +00:00