WebExtension tests expect DevTools to be automatically initialized,
they access DevToolsShim.gDevTools.getTargetForTab in order to open DevTools.
MozReview-Commit-ID: 3VQRlxgBkI0
--HG--
extra : rebase_source : 66fe8aeef5314fe06ac59ae025b1321fcc1195fc
Per definition of this bug/patch, key shortcuts can't be registered anymore.
It mostly means that add-on definition a key shortcut won't keep their key shortcut working.
This shouldn't be an issue on 57 as I don't think WebExtension addon can set a key shortcut via this DevTools API.
MozReview-Commit-ID: G5c8JzaUWoR
--HG--
extra : rebase_source : d9cda8d4af63af795e8f66d3bee7e442bd78d939
Now that devtools-browser is lazily evaluated, we have to create the widget early in devtools-startup.
MozReview-Commit-ID: JanbAPalYE1
--HG--
extra : rebase_source : 2625da986184d5a1f8b3ce293da4e16fdb5ed339
The services.js shim has been moved to devtools-core repo on GitHub
and should be removed from mozilla central.
MozReview-Commit-ID: 3uolLWuU6Lh
--HG--
extra : rebase_source : 98a0506be5df5be56ef03f98162effbf0b1142fb
Stylo might be enabled by either env var or pref. Use the existing
DOMWindowUtils method to test for Stylo instead of the pref to get an accurate
value.
MozReview-Commit-ID: 8p22xCBjHjo
--HG--
extra : rebase_source : 1a5524e22be07a712838ac5a2ac0bec0cc65dfa7
Implements PerformanceTiming, nsITimedChannel, and devtools 'tls setup'
Also captures telemetry on this as we do for all other attributes of timedChannel
Also propogates some null transaction timings onto first real
transaction of a connection
MozReview-Commit-ID: 47TQJYVHnKC
--HG--
extra : rebase_source : a7723962986de0c2ab00d479a22c3f5fd185c8b2
Some tests were failing after switching to ObjectInspector.
Here we remove the ones that are specific to the VariableView, and
fix the "store as global" one.
MozReview-Commit-ID: 4IhNp4MTC2k
--HG--
extra : rebase_source : 60286976e5fd6e7c68e022679effe5a43a5d3845
Because we need to check in an another property from the store for actors to release,
a little refactor of how we deal with actors to be released was needed.
So instead of tracking removed messages from the store, we directly track removed actors.
We can compute this list directly in the reducer, and it even allow us to simplify the enhancer a bit.
Some tests where added to make sure we do handle loaded properties in the store.
MozReview-Commit-ID: 72F2wl3UaLA
--HG--
extra : rebase_source : 974799ef52dd25e8b2d99eb98228190487cc91b2
Remove tests since they were all migrated to jest in Github and will only
lives there now.
MozReview-Commit-ID: 7N8Wuq6sD2I
--HG--
extra : rebase_source : 3f3dba033ed48302094c62ec5f092f7bbf89fa26
Change the URL of the repository to the devtools-core one.
MozReview-Commit-ID: J0WStbVAZ5Z
--HG--
extra : rebase_source : b3fa6f7ae371432b53ba7daad30aa1fae45aecbe
If a SourceMap response header was saved on a style sheet, use it in the
style sheet actor.
MozReview-Commit-ID: GRLCdRCaP5Q
--HG--
extra : rebase_source : 6632acb69a4d1a85ea6ccf3897c0e3be7ae51edd
Add restyle markers to `PrepareAndTraverseSubtree` to cover both initial styling
and part of the work of restyling. Also add restyle markers around the post
traversal work in `DoProcessPendingRestyles`.
A new marker is also added around the change hint processing after the post
traversal.
MozReview-Commit-ID: 43PSyCJLikR
--HG--
extra : rebase_source : 923dd3d5526a7d68ab08f86e6dc233c9c61fa97f
Stylo doesn't have a good equivalent for restyle hints to expose in markers and
the ones exposed for Gecko aren't very accurate either, so we don't want to
expose the restyle hint anymore.
At the same time, several animation restyle tests currently use the hint inside
the marker to check when animation-only restyles have happened. We can preserve
this by changing the data inside the marker to be a flag for whether the restyle
is animation only, which we know for both Gecko and Stylo.
MozReview-Commit-ID: 8L8KU8Ush7P
--HG--
extra : rebase_source : 4eef80653c1ef79ee1539d27fe6a70fbfaf441ad
This patch renames the mozinfo flag 'coverage' to 'ccov' to avoid ambiguity in whether a test is being skipped for linux64-ccov or for linux64-jsdcov. It also removes the 'runtests.py' mozinfo hack and renames all occurrences of 'coverage' that are used for skipping tests in linux64-ccov.
MozReview-Commit-ID: IF2640bDQP7
--HG--
extra : rebase_source : 614020325e30d1ca9e01aaf08479b8a4ffaec888
The whitelisting function thisTestLeaksUncaughtRejectionsAndShouldBeFixed was replaced by expectUncaughtRejection, and existing calls did not take effect anymore.
MozReview-Commit-ID: 3uOxkgWYWEz
--HG--
extra : rebase_source : 6b27b77da78743880529adae7adf4ec2aa64dfea
extra : intermediate-source : 5809a30a0c4817509beb1078cf336d8367b8107a
extra : source : 6f0394b523a66dab444b8551deb8f3c6c81d8f31
Here we make updates on reflow slower (with a throttle) cause we don't
really need to update live.
We also filter all reflows that do not cause either the list of grids or
the current outline to change.
Finally, we also attach NodeActors to GridActor forms (when they are know)
in order to avoid one more round-trip to the server.
Globally, this makes performance of the grid panel far better on pages that
cause many reflows.
Note that this commit also fixes a debounce vs. throttle confusion that
existed in an inspector utils file. The throttle function there was actually
a debounce function, so it was renamed, and an actual throttle function
was added.
MozReview-Commit-ID: GeqgZR0o0E6
--HG--
extra : rebase_source : 6b9719379dcbd4479bded26014aa3742bd75208e
Beta and release might also have e10s disabled, so it's better to show the
notification bar, even if it's less actionable there, so they have some
explanation for the old RDM UI appearing.
MozReview-Commit-ID: L2DATLJN7vb
--HG--
extra : rebase_source : 1e5fb90a6099e55604ed4ea4686600e0d2251242
As DevTools are moving to be an addon and out of mozilla-central, we should remove the
coupling between the mozilla-central code and the DevTools code.
Instead of directly loading and calling the ToolboxProcess, XPIProvider.jsm now uses
events to interact with BrowserToolboxProcess.
MozReview-Commit-ID: HpnMLCILkea
--HG--
extra : rebase_source : 7b090d996fdf25ac364c05e075983454979bdeb5
Here we make updates on reflow slower (with a throttle) cause we don't
really need to update live.
We also filter all reflows that do not cause either the list of grids or
the current outline to change.
Finally, we also attach NodeActors to GridActor forms (when they are know)
in order to avoid one more round-trip to the server.
Globally, this makes performance of the grid panel far better on pages that
cause many reflows.
Note that this commit also fixes a debounce vs. throttle confusion that
existed in an inspector utils file. The throttle function there was actually
a debounce function, so it was renamed, and an actual throttle function
was added.
MozReview-Commit-ID: GeqgZR0o0E6
--HG--
extra : rebase_source : a2792a0ec4cad2034965d36648f0675ae4f52d86
As devtools become optional, nsContextMenu needs to check if devtools are installed before
displaying the devtools-related menu entries.
Rather than loading devtools classing and calling APIs, use APIs provided by the DevToolsShim,
that will stay in mozilla-central.
MozReview-Commit-ID: CxqabTjhckC
--HG--
extra : rebase_source : 1781edcf11316eab7e95cbab834d1bc3230c44d7
Keyboard navigation was broken because we introduced private columns that are never displayed (for compound primary keys) and were not equipped to deal with hidden key columns.
This change gets the first visible column, whether it is private or not so that we no longer have to worry about hidden key columns.
The small change to the keyboard test ensures that the private column is hidden so the test will fail if this feature is broken again.
MozReview-Commit-ID: IB7efHsflGU
--HG--
extra : rebase_source : 06e3283447a7e91641f3d91058fd472d8ca29e8a
This ensures that clicking on a message open the netmonitor panel, with the network
item clicked being selected in the netmonitor panel.
The loadDocument was edited to accept a URL instead of relying on the existence of
a TEST_PATH variable. Callsites where thus modified.
MozReview-Commit-ID: 3dbX1Myxirz
--HG--
rename : devtools/client/webconsole/test/test-network-request.html => devtools/client/webconsole/new-console-output/test/mochitest/test-network-request.html
extra : rebase_source : 06eac0cad3eba9961b61f1a2df2f2932c60dd2bc
Prior to this patch, we were retrieving the message data in the ConsoleOutput
render, for each message. This means that for each message addition, we were
retrieving the data for each message in the store.
This doesn't impact performance if there are not many messages in the store, but
if the store is "full", we might end up calling the function to get those messages
a lot. And since the messages are in an Immutable.OrderedMap, it can be very costly.
Moving the retrieval of the message data in ConsoleOutput allow us to only call this
function when a message is added or updated, which allow us to save some time on
the rendering path.
MozReview-Commit-ID: S4NSSW5Mvw
--HG--
extra : rebase_source : 5262b5b34bb86fec5c14b7056875b8f8b661262a
Changes to Promise tests designed to test .then(null) have been reverted, and the browser/extensions directory was excluded because the projects it contains have a separate process for accepting changes.
MozReview-Commit-ID: 1buqgX1EP4P
--HG--
extra : rebase_source : 3a9ea310d3e4a8642aabbc10636c04bfe2e77070
Add a test case to measure streaming time when the store already hit the log limit so
we can have data about pruning.
Switch to performance.mark and performance.measure for time measurement instead of the
custom timeit function we had.
This allow us to have precise data, and also those are written in the profile and then
shown in perf-html, so we can have a better overview of what's going on during the test.
MozReview-Commit-ID: 2nNmukxmUso
--HG--
extra : rebase_source : c8dca67060c2bf6a61e32c78e9fb35b24d7801a9
Add a test case to measure streaming time when the store already hit the log limit so
we can have data about pruning.
Switch to performance.mark and performance.measure for time measurement instead of the
custom timeit function we had.
This allow us to have precise data, and also those are written in the profile and then
shown in perf-html, so we can have a better overview of what's going on during the test.
MozReview-Commit-ID: 2nNmukxmUso
--HG--
extra : rebase_source : 298387e0f33ff226f6d096fd8786f29ddbd5a56f
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : b6573f8e2001f91d0e5a50f6376b191459549e94
extra : intermediate-source : 0411e687044ecc7b56684196238e6e6e68a9d685
extra : source : 8d53be05afc59519c5ce8cfae96d284a972fda71
In the console, we were assuming that eventTiming was the last
of the eight networkUpdate that happen for a given network request.
Unfortunately, we can't ensure the order in which those updates come,
so the test was intermitently failing when eventTiming was fired
before other updates.
To fix this, we don't look for a specific update, but rather check that
all of the 8 updates happened.
MozReview-Commit-ID: Iv0TIHoqkyv
--HG--
extra : rebase_source : 129a2edd1725e8eddc8ea20de3d38e1bc5f27f87
Use DevToolsShim to access devtools APIs from webextensions code.
For webextensions tests using DevTools, tests are accessing DevToolsShim.gDevTools
which is fine for test purposes.
MozReview-Commit-ID: 66gFV98xvpf
--HG--
extra : rebase_source : 05734afae4368c5d7e4682b5fae1b8f3e4417220
On Skia / OS X using a large number as workaround for infinite lines makes
the canvas really slow; here I removed the hack, calculating the proper
intersection with the canvas' boundaries for the infinite lines. That should
greatly improve the performance for transformed grid.
MozReview-Commit-ID: Ae1GyxIhf3l
Some APIs and methods still used by the addon sdk are not worth exposing
or migrating to mozilla-central given that this is only intended for
release 56 (after that, legacy extensions will no longer be supported).
For those APIs, we create a simple wrapper in DevToolsShim and moved the
implementation to framework/devtools
MozReview-Commit-ID: 8LiiptqO0NI
--HG--
extra : rebase_source : 3e4832bcaffa92d64e9d2490bcc0250bc05573c1
Andy McKay
Mark Striemer
Jan Odvarko
Sebastian Hengst
Patrick Brosset
Wes Kocher
Oriol
Joel Maher
Jason Laster
Brian Grinstead
Alexandre Poirot
Julian Descottes
J. Ryan Stinnett
Ryan VanderMeulen
Vangelis Katsikaros
Carsten "Tomcat" Book
Junior Hsu
Yoshi Huang
Nicolas Chevobbe
Brian Birtles
Mike Park
Swapnesh Kumar Sahoo
Patrick McManus
Tom Tromey
Micah Tigley
Geoff Brown
Rajesh Kathiriya
foxt7ot
Espen Henriksen
Luca Greco
Phil Ringnalda
Gabriel Luong
Greg Mierzwinski
Christoph Kerschbaumer
Jim Mathies
Frederik Braun
Towkir Ahmed
Michael Brennan
Paolo Amadini
Vincent Lequertier
Ricky Chien
Michael Ratcliffe
Tim Nguyen
Nathan Froyd
Haik Aftandilian
Yury Delendik
Ruturaj K. Vartak
Honza Bambas
Masatoshi Kimura
Jan de Mooij
Matteo Ferretti