If a reply comes from source-map-url-service but the tooltip has already
been destroyed, don't try to emit the event-tooltip-source-map-ready
event.
MozReview-Commit-ID: EKrT7V4qLJq
--HG--
extra : rebase_source : e3c4e4cbebdb9adbc1b414c14b9df241abba009c
asm.js and wasm frames were not being correctly identified as user
content in the perf devtool. This patch correctly finds blob urls that
were being mis-identified as platform content, and wasm frames, which do
not have any identifying information other than their function name
containing wasm-function.
MozReview-Commit-ID: 4DjqATCKBK0
--HG--
extra : rebase_source : 0c261074d0b786d99e0a6a4dbdd81e3606b66081
The whitelisting function thisTestLeaksUncaughtRejectionsAndShouldBeFixed was replaced by expectUncaughtRejection, and existing calls did not take effect anymore.
MozReview-Commit-ID: 3uOxkgWYWEz
--HG--
extra : rebase_source : 5a10a3ebbfe0ce2a801330041f95447c313a9a70
extra : source : 6f0394b523a66dab444b8551deb8f3c6c81d8f31
The whitelisting function thisTestLeaksUncaughtRejectionsAndShouldBeFixed was replaced by expectUncaughtRejection, and existing calls did not take effect anymore.
MozReview-Commit-ID: 3uOxkgWYWEz
--HG--
extra : rebase_source : 3a7720091180a770b32b595f8094c0d20170166d
In the Bug 1335055, accessibility features were added for re-focusing on
a TreeNode when it was unmounted. Unfortunately this is incompatible
with how the Tree provides a virtualized view, where it only has DOM
nodes on the page that will be visibile when things are scrolled. So
when a view is scrolled down, the TreeNode components get unmounted.
The focused node is still technically focused, but the actual component
is no longer mounted and present on the page. This causes the focus to
incorrectly jump around as the user scrolls down the page.
MozReview-Commit-ID: 64hlwCax0Ej
--HG--
extra : rebase_source : 60ba0ac37fc61bb3fc874230cc54e6147bd1b13b
Added gDevTools.getTheme() to provide the theme name, and a gDevTools "theme-changed"
event to provide a notification when the theme is changed.
MozReview-Commit-ID: EeUAmtyPpUy
--HG--
extra : rebase_source : 38515c6fb4d4294aa20d862da0c1bb96f17cd99a
nsIPrefBranch getters support an optional default parameter.
If provided, the getter should not throw in case the pref is not defined, but
instead should return the default value.
MozReview-Commit-ID: FfWPmOC6bFI
--HG--
extra : rebase_source : a18d53c897bb7483997ed9e2faa9e737b4c644e8
This changeset makes the classname variables-view-scope no longer able to
receive the focus. When tabbing through the variables view, going from the
variables-view-scope to the first variables-view-variable item has no
visual impact as their container occupy the same space.
Having to TAB twice without providing user feedback feels buggy.
MozReview-Commit-ID: It4EOV45A40
--HG--
extra : rebase_source : 5f865283613073fe72de98d012274a8d74dfe88f
This changeset modifies devtools-browser.css to import:
- commandline-browser.css (needed for GCLI)
- responsivedesign.css (needed for the old RDM)
These files are no longer included in the main browser.css files.
devtools-browser.css is also no longer loaded by browser.xul.
Instead it is dynamically loaded when devtools need the browser stylesheet:
- when creating a side or bottom host (need the splitter)
- when opening gcli
- when opening the old responsive design
devtools-browser.js keeps track of the browser stylesheets loaded in the
various tracked windows and will remove the stylesheet when the window is unloaded.
MozReview-Commit-ID: AL3CxS7mvdO
--HG--
rename : devtools/client/themes/commandline.inc.css => devtools/client/themes/commandline-browser.css
rename : devtools/client/themes/responsivedesign.inc.css => devtools/client/themes/responsivedesign.css
extra : rebase_source : a4a1e993657ff3abcc975249812723ab46bc84a8
