This adds a menu to the RDM global toolbar to allow the user to control whether
the page reloads in response to various state changes.
This also changes the default behavior to _not_ reload, so that we avoid losing
changes that might have been made in DevTools.
MozReview-Commit-ID: 86h5cB5dify
--HG--
extra : rebase_source : ebb4f86da4407772704a9fc06b4083b39cf61290
Currently, if you open the Inspector on some page, then enter RDM, the Inspector
will "reboot" (reload all panels) because it believes the document has reloaded.
However, it's not really true in this case. Instead, it's an artifact of the
pagehide / pageshow events that are triggered when swapping frames like RDM
does. Bug 1438697 adds a chrome-only property that we then use here to
distinguish this case.
MozReview-Commit-ID: Ks42QayVnij
--HG--
extra : rebase_source : 91739a5db2774073e723b1daf43bc5242755fc43
Note that this patch also replaces legacy VK_* with KEY_*, and replaces
synthesizeKey() for inputting some characters with sendString() because
it's better and clearer what it does and it sets shiftKey state properly.
MozReview-Commit-ID: De4enbjux3T
--HG--
extra : rebase_source : 2296b84bff8e22f01eeb48cd8614fac5db11136a
We can now remove the extra `.browser-container` element around the frame. It
was only here as a way to invoke React's `innerHTML` for real content.
MozReview-Commit-ID: 1wnv7SJmjTd
--HG--
extra : rebase_source : 12435e53d069d23adc22de4b1ba0259912ad6027
Now that we have React 16 (which includes support for custom attributes instead
of a fixed whitelist), we can create the browser frame in the "usual" way, as
opposed to this `innerHTML` workaround.
MozReview-Commit-ID: GwZVNIqF1QC
--HG--
extra : rebase_source : eec7a2c54638420b1a7adc27f25e1f0237eaa30e
Now, callers of EventUtils.synthesizeKey() don't need to specify
KeyboardEvent.code value anymore if they assume that active keyboard layout
is US keyboard layout.
Note that this patch changes the meaning of only test_bug551434.html.
Some callers in it don't match the key value and code value but that looks
like that they don't checking such odd keyboard events. So, they must be
bug of the test.
MozReview-Commit-ID: Itxo7yZ9rkK
--HG--
extra : rebase_source : 856ef3715c924ca16e993ea57d92d1243b5cc6be
In RDM's test for device pixel ratio overrides, there was a race condition where
the document's pixel ratio might change at the same time as it reloads (because
we trigger reloads for certain device changes). The step that listens for the
new pixel ratio to be applied was missing the case where after a reload, the
pixel ratio is already set to expected value, leading to intermittent hangs.
To resolve this issue and simplify things overall, we now explicitly wait for
reloads where we know they will happen first. Then, we check the pixel ratio
state after that, using the expected value we want to find.
MozReview-Commit-ID: DZYFT4AzaJd
--HG--
extra : rebase_source : 58dce8839a1f9d9a0064e2114e3a4811a437d8b7
This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <
J. Ryan Stinnett
Masayuki Nakano
Mark Banner
Mike Ratcliffe
Alexandre Poirot
Andreea Pavel
Andrew McCreight
Kris Maglione
Florian Quèze
abhinav
Bill McCloskey
Dorel Luca
Brian Grinstead
Julian Descottes
Ryan Leake
Nicolas Chevobbe
Simon Van Accoleyen
Miguel Useche
Sebastian Hengst
Wes Kocher
Tom Tromey
ZER0
Christoph Kerschbaumer
Nathan Froyd
Matt R
Ryan VanderMeulen
Mats Palmgren
Carsten "Tomcat" Book
Ben Kelly
Dão Gottwald