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
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
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
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
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
