Boris Zbarsky 8fd50f23d4 Bug 1379762 part 2. Use a more reliable test to figure out when we can skip firing onload in nsDocumentViewer::LoadComplete. r=smaug ... Unfortunately, GetRestoringDocument can be false by the time we reach LoadComplete, if part of the restoration process managed to set up and then remove onload blockers. If that happens, we still don't want to fire a load event for a document that has already has one fired. Note that we could also use a boolean on the document to record whether we've fired a load event, as long as we were careful to unset it when the readyState transitions backwards from COMPLETE (e.g. document.open). It's not clear which approach is more robust.		2017-07-17 23:21:41 -04:00
..
base	Bug 1380227 - Avoid many UTF16toUTF8 and UTF8toUTF16 conversions in nsStringBundle. r=emk.	2017-07-12 15:13:37 +10:00
build	Bug 1363327 - register about:debugging dynamically using a manifest;r=ochameau	2017-05-26 10:09:42 +02:00
resources/content	Bug 1334831 - script-generated patch to use .remove() instead of .parentNode.removeChild, r=jaws.	2017-01-30 08:10:22 +01:00
shistory	Bug 1372405 - Provide names for all runnables in the tree (r=froydnj)	2017-06-26 14:19:58 -07:00
test	Bug 1379762 part 2. Use a more reliable test to figure out when we can skip firing onload in nsDocumentViewer::LoadComplete. r=smaug	2017-07-17 23:21:41 -04:00
moz.build	Bug 1350496 - add BUG_COMPONENT to docshell/* files. r=overholt	2017-04-09 05:43:52 -04:00