For browsers in e.g. panels, we can't really make decoder doctor work well, so we simply elect to only listen for such messages within tabbrowser browsers.
MozReview-Commit-ID: Frrhf6AOgAy
--HG--
extra : rebase_source : c3855599db67f25ab39dae1f7693d8c8958dee1e
For CSS files which were used via both chrome:// and resource://, I converted
all usages to resource:// and removed the chrome:// copy to reduce file
duplication.
I believe most DevTools CSS could be using resource:// throughout, but that's
left as follow up work for now.
MozReview-Commit-ID: G7oxZqjodwv
--HG--
extra : rebase_source : d6ae487f35cdeddd32aa96d95d62113ba0565b2a
Also ensure the telemetry origin is set correctly when the searchbar popup first opens.
MozReview-Commit-ID: Fd7hc6BTVVQ
--HG--
extra : rebase_source : 0e4666f99ecab1b2de0b729290e9f6dac96ae40a
This removes the obsolete toolkit directory. A few references to dialogOverlay
have been updated to just used <dialog> directly. The InlineSpellCheckerUI var
has also been moved directly to browser.js and defined as lazy getter.
MozReview-Commit-ID: JZfi0W2wqCL
The popuphiding / popuphidden events are fired synchronously when the popup manager
decides we're doing a "rollup" (closing the popups due to "outside" events). In the case
of this bug, the "outside" event is a click on the input element in content.
Here's the kicker though: we handle that popuphidden event and queue a message to content
_before_ the mouse event that caused the roll-up is dispatched to content. This means that
browser-content.js hears that the popup closed due to popuphidden first, sets its internal
state of popupClosed to true, and then the MouseDown on the input field is processed. The
nsFormFillController then queries browser-content's AutoCompletePopup, sees its closed,
and tells the parent to open it again.
This patch adds the norolluponanchor attribute to the panel, which causes us to ignore the
rollup event if it happens to be targeted within the anchor rect. This means that we need
to trust content to tell us to close the autocomplete popup if the input is clicked when
the popup is open (and this is what bug 1183037, which this bug depends on, does).
MozReview-Commit-ID: 4A9qVfTYIUz
--HG--
extra : rebase_source : 113049adfd07b3ddd91b92b5a156d75465e1e8c9
Drop linting of the .eslintrc.js config files.
Fix some minor errors in the code (missing let/const, undefined vars).
Let eslint know that some files get their globals from other places (typically via xul script tags).
MozReview-Commit-ID: CwxuwPtRUr6
--HG--
rename : browser/components/contextualidentity/test/browser/.eslintrc.js => browser/components/syncedtabs/test/browser/.eslintrc.js
rename : browser/components/contextualidentity/test/browser/.eslintrc.js => browser/extensions/webcompat/test/browser/.eslintrc.js
extra : rebase_source : 9026aac49953d941853022cbab3e33d7d2f2fa21
If a hidden tab is added at the end of a tab bar with enough tabs to show the
scrollbutton-down arrow, it would cause the arrow to highlight incorrectly,
suggesting there an additional tab to find, but in reality there isn't since it
is hidden. This can occur with DevTools Responsive Design Mode which makes use
of hidden tabs.
By skipping `_notifyBackgroundTab` for hidden tabs, we avoid this issue because
we no longer attempt to highlight the arrow.
MozReview-Commit-ID: 2FoJ7UouJCL
--HG--
extra : rebase_source : 3dea801063624580317076624d8de84f99467317
This introduces LoginFormFactory which wraps FormLikeFactory for use with login-specific contexts.
MozReview-Commit-ID: 6rPz5JOy3Yp
--HG--
rename : toolkit/components/passwordmgr/LoginManagerContent.jsm => toolkit/modules/FormLikeFactory.jsm
extra : rebase_source : b2a28803def0dce3de4a01db5bdbc3217c5d0f83
Updating the UI here doesn't seem useful, but it's such an edge case that we
can live with this assumption in the test.
MozReview-Commit-ID: JZ83wA4KpwV
--HG--
extra : rebase_source : 982765163df18ddd8a72412057516ed4d6946a64
extra : source : 5fe7b3e0d134f58455626db281e75a72f9a3961a
