It was using `window` which refers to the browser window, but we actually want to synthesize
the click in the devtools window.
MozReview-Commit-ID: KeIwq3JIJin
--HG--
extra : rebase_source : c769229d19661370d5448f0b5b236ce8b2eb91c4
- Access nsISSLStatus directly as a member of nsITransportSecurityInfo
and nsISecureBrowserUI. This is part of a larger effort to consolidate
nsISSLStatus and nsITransportSecurityInfo.
- The TabParent implementation of GetSecInfo will always return null.
- Removed unnecessary QueryInterface calls
- Style adherence updates
MozReview-Commit-ID: Dzy6t2zYljL
--HG--
extra : rebase_source : fbfbcf7608efbfb35c9be4018ff0f4e70b2768d2
Since codeMirror jsterm is becoming the default, we explicitely
set the pref to false before each jsterm test so they run with
the 2 version of the component.
MozReview-Commit-ID: 2qxIcRlIS9M
--HG--
extra : rebase_source : 025dcf3ee32969db87621f6c92e284a21e2a51e2
The actual fix for this issue will come in a future
reps bundle when https://github.com/devtools-html/debugger.html/pull/6705
gets merged.
But, I do want this change to be uplifted to release, and it should be
easier to only apply this simple change than the whole next release
which would contain unrelated code changes.
Also, this patch introduces a test to make sure we don't ever regress
this.
MozReview-Commit-ID: 3QPrx3TLln0
--HG--
extra : rebase_source : 9a62da36af01506e9290d059a2aa3a4a7c8bc75f
The optimization this code was working around has now been fixed.
Differential Revision: https://phabricator.services.mozilla.com/D2419
--HG--
extra : rebase_source : 586f19d9254c4aab88f54bd7b4122b613e1b39e8
extra : histedit_source : 4555f3e34c9863ae9db41f437f2c9ce6a3fed006
The popup was properly sized (and positionned), if it was previously closed,
which could led to layout issues when changing the autocomplete popup (e.g.
by typing a ".").
We now always call openPopup when there's items in the popup so it's always
properly sized.
I'm expecting some performance overhead here, but I'm working on another bug
that should make the popup faster.
A test is added to make sure we do resize the popup as needed.
MozReview-Commit-ID: K7dOllMrq0b
--HG--
extra : rebase_source : 95cf1a6c6f21ee253756f4f26a2fab89887f14b6
- Access nsISSLStatus directly as a member of nsITransportSecurityInfo
and nsISecureBrowserUI. This is part of a larger effort to consolidate
nsISSLStatus and nsITransportSecurityInfo.
- The TabParent implementation of GetSecInfo will always return null.
- Removed unnecessary QueryInterface calls
- Style adherence updates
MozReview-Commit-ID: Dzy6t2zYljL
--HG--
extra : rebase_source : b15f75e39d04c8485b4eb63416fd1f1e4175fafe
As per https://design.firefox.com/icons/icons/android/open-in-new-24.svg
but rather adapted to match the proportions of the other icons and fit on
a 16x16 grid.
MozReview-Commit-ID: 9bGWiBjX1P4
--HG--
extra : rebase_source : 1b87badf8ed045368c7f3d003c3c4f4611ab6a4b
This removes AutoMaybeEnterFrameRealm. Most places pass cx->realm->principals: it preserves behavior when the (possibly wrapped) SavedFrame and cx are same-compartment. The main exception is the JSStackFrame DOM bindings code where we have to be a bit smarter about which principals to use.
getCssPath and getXPath will need to reuse the same logic as findCssSelector
to handle shadowDOM support.
This patch moves the methods next to findCssSelector, in toolkit's css-selector.js
to avoid duplicating logic between devtools/ and toolkit/
The content of the methods is stricltly the same, except for the Node global
not available in css-selector.js. Instead we use `ele.ownerGlobal.Node` here.
MozReview-Commit-ID: J0KuORWLUoO
--HG--
extra : rebase_source : 26a1801670e5554577f0f77b62667527f7b497bb
getCssPath and getXPath will need to reuse the same logic as findCssSelector
to handle shadowDOM support.
This patch moves the methods next to findCssSelector, in toolkit's css-selector.js
to avoid duplicating logic between devtools/ and toolkit/
The content of the methods is stricltly the same, except for the Node global
not available in css-selector.js. Instead we use `ele.ownerGlobal.Node` here.
MozReview-Commit-ID: J0KuORWLUoO
--HG--
extra : rebase_source : d6fab834be4fb6ad9ba1cd73acf960cf0fe0d4d5
This patch will remove the dotted style focusring from TabBar. We have same tab
bar in the toolbox, but this tab has removed this style already.
(For detail, see bug 1444793)
MozReview-Commit-ID: CyazZkvKR6H
--HG--
extra : rebase_source : 821e606f54bfceba124af9d9c2585296f2ebc40e
Adapt inspector test to the new order of the search results.
This was an easy task since we were already flipping the
expected results to make the test more readable (which makes
me think that this is the "natural" order).
MozReview-Commit-ID: DpxW2O1eOi4
--HG--
extra : rebase_source : 8d579c94bdaaee396a29b4674d4f9764bcadbb5d
extra : source : 96c82bb5fa591470483263aea55fa33a10192afc
For some reason, we were flipping the search result, which
was not ideal in the inspector. This patch changes this to
show results in the same order the server return them.
MozReview-Commit-ID: Ak9FnrrW8z5
--HG--
extra : rebase_source : 0846cda90ac45c70a9ee5cd49f64f1894863ec5c
Some tests needed to be adapted to the new alpa-sorted
autocomplete popup.
MozReview-Commit-ID: 3GOAJqH0CvD
--HG--
extra : rebase_source : ca9bafa6e78f2a1609618e5c258db0358a006300
The autocompletion results were flipped in order to have them in reverse
order since the popup was displayed at the top of the input.
We do not want to do that anymore because of two reasons:
- I couldn't find any example in the wild doing the same thing, thus
we were making the user switch their habit to use it
- Bug 1136299 will make it so that the popup could be displayed either
at the top or at the bottom of the caret. We shouldn't have different
sorting for those different cases as it would make the popup even
harder to use.
MozReview-Commit-ID: CAzsKIaeKgV
--HG--
extra : rebase_source : 967e43e5d86f7f35945ba5742c1a25823a2d0064
Previously, we were trying to select the item the closest
to the input used for the autocompletion. It was causing
some weird behaviour when the popup wasn't displayed at
the expected position.
Always selection the top-most item seems will avoid those
cases, bring us consistency across the toolbox as well as
with other tool having autocompletion (code editors, Chrome, …).
The autocomplete-popup test is modified to assert the new behavior.
MozReview-Commit-ID: DhNovX51KRO
--HG--
extra : rebase_source : cfb2ebaaed23ce5c51ef9d8f447f3fabe0a04a49
The new "tooltip.css" file allows styling the default tooltip, which is created as native anonymous content.
MozReview-Commit-ID: ADWsFTNPfhw
--HG--
rename : toolkit/themes/linux/global/popup.css => toolkit/themes/linux/global/tooltip.css
rename : toolkit/themes/osx/global/popup.css => toolkit/themes/osx/global/tooltip.css
rename : toolkit/themes/windows/global/popup.css => toolkit/themes/windows/global/tooltip.css
extra : rebase_source : bd79b86fb44ac0dc77d0d21fdc003105da6f43eb
extra : intermediate-source : a06a200098013d5dbc42c2431f845ca1dd8b0b76
extra : source : 4d511f7fc5b5c16fdfea91242dea6086cd57c8c3
This is probably the last thing we will ship since it needs the most spec work.
MozReview-Commit-ID: LLmDBLCsCBJ
--HG--
extra : rebase_source : c06752c9201a9ede87e1ac200ab12577bf784ce6
This preference controls whether authors are allowed to specify animations
without a 0% or 100% keyframe.
We intend to ship this soon but this preference acts as a safeguard in case we
discover we need to disable it.
This feature is very convenient and commonly used so this patch ensures it is
always enabled for system content.
MozReview-Commit-ID: BHTsuS2xO61
--HG--
rename : dom/animation/test/mozilla/file_disable_animations_api_core.html => dom/animation/test/mozilla/file_disable_animations_api_implicit_keyframes.html
rename : dom/animation/test/mozilla/test_disable_animations_api_core.html => dom/animation/test/mozilla/test_disable_animations_api_implicit_keyframes.html
extra : rebase_source : 04fd93dd26a4765c14b0b22febdb0311b650ea59
We don't intend to ship this in the near future until the integration with
AnimationWorklet is clear (although we might ship a read-only version).
That said, we use this feature extensively internally (e.g. in DevTools etc.) so
we enable this feature for system callers.
MozReview-Commit-ID: AhB7ZmU1Xzw
--HG--
extra : rebase_source : 630d7dc56b44a9261bb34aa5417cb9b7050efba4
