The variable MOZ_DEVTOOLS_ALL was only used in order to register about:debugging and should
no longer be needed.
MozReview-Commit-ID: 16di87Cad2n
--HG--
extra : rebase_source : 19be6ea118c00293e36b4a1d7e3441499ecb3c62
This flag is for when we've loaded a URI in a remote type that is not the default
for compatibility reasons (for example related http in the file content process).
So that we can load the history entry in that same process as well.
This part is mainly to mark the channel as urgent-start if src related
attributes in HTMLImageElement and HTMLInputElement is set and the channel is
open due to user interaction. Unfortunately, we cannot just check the event
state just after creating channel since some loading image tasks will be queue
and execute in stable state. Thus, I store the event state in elements and
pass it to the place where create the channel.
MozReview-Commit-ID: GBdAkPfVzsn
--HG--
extra : rebase_source : 715352317b4b600f8a7f78b7bc22b894bb272d27
There's one redudant NS_ShouldCheckAppCache(nsIURI*, bool) is not used
anymore. Also we remove the extra usePrivateBrowsing argument, since we
can get this information from nsIPrincipal.
Convert the singleton HistoryTracker implementation to a per-nsSHistory based
implementation so that it can be bound to a TabGroup.
MozReview-Commit-ID: 7cMtArsO5lQ
--HG--
extra : rebase_source : 3711bc7f7afaa40772035e24270d4fde1d17924a
Re-order includes to meet gecko's coding style, and move bool data members
to the bottom for slightly better alignment (nsSHEntry down from 192->176,
nsSHEntryShared down from 208->200 on a Linux64 build).
MozReview-Commit-ID: CG1M6Hh39uI
--HG--
extra : rebase_source : 5762a8a3536805e2b15b71425a9376c191cf16cb
This test was accidentally taking advantage of the fact that closing a tab will result
in a nested event loop while waiting for the permitUnload messages to be sent back and
forth from the content process. This meant that the message that tells the parent that
the browser (which is having its history set) can now go back had a chance to be received
by the parent.
With the patches in bug 1336763, we're no longer spinning the event loop if the closing
tab doesn't have a beforeunload event handler in it, so we need to wait for the browser
to report that it can go back before actually sending it back in order to avoid a
test failure.
MozReview-Commit-ID: Lpl55iErrvf
--HG--
extra : rebase_source : 87b2d6a0fb448f729b82860de9d17c0db26097e7
The urgent-start classification will tell the network requests scheduler to perform it with the highest priority and also ignoring any parallelism or overall connection limits. Doing this for top level document load could increase the responsiveness to users.
TimeStamp::ProcessCreations()'s aIsInconsistent outparam is ignored by the
majority of its caller. This patch makes it optional. Notably, this makes
ProcessCreation() easier to use in a constructor's initializer list.
We only need metric from top level content document, but we dont have
any information about it in nsDOMNavigationTiming, so I add a weak
reference which points to nsDocShell.
MozReview-Commit-ID: GiJigRLYHNV
Marco Bonardo
Geoff Brown
Ben Kelly
Christoph Kerschbaumer
Carsten "Tomcat" Book
Julian Descottes
Ryan VanderMeulen
Honza Bambas
Samael Wang
Bob Owen
Wes Kocher
Gijs Kruitbosch
Milan Sreckovic
Tom Tung
Boris Zbarsky
Yoshi Huang
Olli Pettay
Masatoshi Kimura
Mike Conley
Kershaw Chang
Nicholas Nethercote
Paul Bignier
Wei-Cheng Pan