…e key shortcut is used in the Browser Console;r=jdescottes
In the old frontend `this.window.close` worked since webconsole.xul was used for both the web console
and browser console. The new frontend is implemented in HTML (webconsole.html) but for the browser console
we wrap that in a XUL document (browserconsole.xul) to support window management and other XUL features.
So when the HTML frontend receieves cmd/ctrl+w, we now call the `close` function for the XUL window instead.
MozReview-Commit-ID: 5j9rimTC2f8
--HG--
extra : rebase_source : dc1b444b22a2c8214e4dbf21a3a4972be2249fc5

…m running on scrollbars in content;r=dao,smaug
The events that get silenced here are already covered for native anonymous content
by IsEventStoppedFromAnonymousScrollbar.
In trees, where <xul:scrollbar> and <xul:scrollcorner> are part of the DOM, copy the
handlers over into attributes on each instance.
MozReview-Commit-ID: Huk5nFC7Qua
--HG--
extra : rebase_source : f5e596f04c6a2022b9d6019d49e61bf64422f912

- bundle_browser_region is already unused so that's just removed.
- After the previous changeset, bundle_browser is referenced only in utilityOverlay.js,
where it's used for the context menu's "Open Link In New Container Tab" submenu.
By updating that one consumer to use Services.strings.createBundle directly we can
remove all instances of the bundle_browser node (overlay and otherwise), and chip
away at the baseMenuOverlay file.
MozReview-Commit-ID: KylUwBRNciS
--HG--
extra : rebase_source : 0ba6478a55111e77a77da40c15d74d9c6c9339c6

…ingbundle-like API;r=Gijs
This will allow us to not rely on an actual <stringbundle> while still avoiding a mass rewrite
of code that accesses gNavigatorBundle with the more awkward API exposed by gBrowserBundle.
MozReview-Commit-ID: 2B4smbo1xZP
--HG--
extra : rebase_source : 0f2eef9178cb61802f158efe88b82a723f5e082e

…yans
While this feature is still being worked on, it's nice if the BT is rendered
properly (there are currently issues with iframe sizing that make it hard to
use the inspector).
MozReview-Commit-ID: AULRq2N6Miv
--HG--
extra : rebase_source : b7596abe13bb8c0f5a3ea488dc84c8736614885d

…mode;r=Gijs
With emulated flex display we wrap inline-level children into anonymous
wrapper-blocks, and those wrapper blocks serve as the flex items. Using
display: block and then resetting the hardcoded width/height does the trick.
MozReview-Commit-ID: Grh1KsSmngP
--HG--
extra : rebase_source : d0792b19387e50d7c70a50a741c060655d4a3669

This is needed because DOMParser is invoked on some fixture HTML that contains an
<svg> element (Walmart/Payment.html). When this happens **and** there is
a declaration for `color: MenuText` in a UA stylesheet (which is added in the next
changeset), there is a graphics crash. This is fixed in the new headless mode,
so this changeset forces the directory to run in it.
MozReview-Commit-ID: 9T8eFOW4xoz
--HG--
extra : rebase_source : d0cd013c2d1a980406c96a3fd6243ff9d2f33ed3

…ons, and styles on menuitem-iconic-left;r=dao
This is needed because menu.css is now loaded as a document style and rules there are overriding some in
panelUI.inc.css. There are plans to deprioritize menu.css in Bug 1420229, at which point this code can be removed.
MozReview-Commit-ID: CF9Ixgqob8
--HG--
extra : rebase_source : 10190b2d356fde01e62237b383002468efe8ffca

…ion mode;r=Gijs
There are still known issues with the browser chrome when emulating, but this changeset is
done in service of getting the UI to be close enough to start running Talos tests against
it in Bug 1425330.
MozReview-Commit-ID: B0w1aOmi4FJ
--HG--
extra : rebase_source : e8b13f9203f0e368fb6f36bc9d2059fff7061b54

…istbox gets the COMBOBOX_LIST role;r=surkov
In the next changeset we will remove the nsIDOMXULPopupElement interface, which
was only used to make sure that this role is set. There wasn't a test covering
this case yet, so this changeset adds one.
Note that we are using a mochitest-browser test as opposed to directly testing
markup like `<panel><richlistbox /></panel>` in a mochitest-chrome test so that
we'll actually be able to catch a regression if the markup for the awesomebar changes.
MozReview-Commit-ID: KGaxQZTDq69
--HG--
extra : rebase_source : 671b718fd010b5f6a2036a695d2c4c03c8b64654

…ylesheet;r=bz,Gijs
This provides a place for current XBL stylesheets to be loaded without using XBL <resources>,
that load as a UA sheet instead of loading them as document sheets. This makes the styles
apply more similarly to XBL, in that they are less specific than document styles.
MozReview-Commit-ID: 3ewomJZMbrk
--HG--
extra : rebase_source : 8d8d837872947daa8f601e7d32de118655dabdde

Key accessibility off of the tag name instead of the role attribute
and load styles in global.css instead of <resources>
MozReview-Commit-ID: Epv0rHHzbz0
--HG--
extra : rebase_source : 2239c8ccca8d899b4c4144faab7212f120f00e23

The only time menucaptions are created are for optgroups, and they
always get instantiated as menucaption-inmenulist. Flatten the
inheritance here to get rid of a binding.
MozReview-Commit-ID: KWzor0QDdma
--HG--
extra : rebase_source : a87ea48a4c6815ec6bdb53925283a9c1ed89f5a2