Remove previous helper APIs:
- currentFlavors()
- getData()
The only consumer for both APIs was in devtools/cient/inspector/inspector.
The logic was:
- call currentFlavors()
- if clipboard contains:
- "text/unicode"
or
- "text/html" but not "image/png"
- then call getData()
But actually calling getData() without any argument means that unless "image/png"
flavor is available, we will always use the "text/unicode" flavor.
(see current code for sdk helper: http://searchfox.org/mozilla-central/rev/09c065976fd4f18d4ad764d7cb4bbc684bf56714/addon-sdk/source/lib/sdk/clipboard.js#204-209)
If the text/unicode flavor was available at the same time as image/png, the code
would have returned the image data, which is probably not what we expect in the
context of the inspector.
I think we should explicitly request for text/unicode. So this patch introduces
a new getText() api in the devtools clipboard helper, which is a simplified version
of the sdk get() helper. We could always extend it to also support text/html.
MozReview-Commit-ID: E3JVj9boVKe
--HG--
extra : rebase_source : 3f1aecd05dacba5cd1a3af6025bbf82d51d49821
DevTools should not execute any code on the browser startup. Loading preferences takes
a non negligeable time and should be deferred to the devtools initialization.
For all devtools entry points, Loader.jsm is always loaded first, so it is safe to
load the preferences here.
MozReview-Commit-ID: Hg4VBj2LqPo
--HG--
extra : rebase_source : 86bfef7e13ecf52b9b8c761fbf7352af42a6bced
In this patch:
- register webide properly
- register localization
- add processing indicator in jar.mn for pref files (details below)
The preferences files still contain processing instructions, that we manually interpret when loading
prefs. Keeping the * processing indicator will avoid triggering warnings in tests scanning
javascript files for issues such as browser_parsable_script.js
MozReview-Commit-ID: 8WYUvbtMNn5
--HG--
extra : rebase_source : 18b13c0d6d1065e141650edb5a3a0b1e7b09a5f8
These two tests just creates a dummy window, however it makes the test
more difficult to write if we just simply use a seperate file for them.
Because these are chrome: tests, and they are opening a content window,
for the chrome side, it won't receive the window.onload because they are
not the same origin.
For the content side, it cannot access 'postMessage' because it looks
there's some protection when trying to read chrome object.
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
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
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
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
