This adds missing preferences to mocha-test-setup.js, and
add URLSearchParams to the global object if it's not
defined there (e.g. in Node < v.10.0.0).
Differential Revision: https://phabricator.services.mozilla.com/D25044
--HG--
extra : moz-landing-system : lando
`Array.map` triggers a deprecation warnings, and it
turns out we can use `.map` directly on the objects
we were calling `Array.map` on.
Differential Revision: https://phabricator.services.mozilla.com/D25506
--HG--
extra : moz-landing-system : lando
If there's at least 2 content blocking messages displayed
for a given page navigation, we display a warning group
containing the messages, collapsed by default.
This means we need to move or insert those warning messages
at the right position in visibleMessages, either when they're
added, or when we expand a group.
Two mochitest are added to make sure this works as expected,
one for generic warningGroup features (expanding, group per
navigation session, …), and another one specifically for
content blocking warning group, where we check that every
type of content blocking message can be grouped.
The grouping won't occur unless the groupWarnings preferences
is on.
Differential Revision: https://phabricator.services.mozilla.com/D23552
--HG--
extra : moz-landing-system : lando
This component will be used to render warning groups messages.
We also add a `inWarningGroup` prop to the `Message` component
so warnings that will be displayed in such warningGroup can
be styled differently (no warning icon, a different color for
the indent).
Add some utils functions and constants to check if a message
should be a warning group.
Differential Revision: https://phabricator.services.mozilla.com/D23551
--HG--
extra : moz-landing-system : lando
This will be used to enable groups of warning messages (Tracking Protection,
CSP, CORS, …).
Differential Revision: https://phabricator.services.mozilla.com/D23550
--HG--
extra : moz-landing-system : lando
Improves spacing and alignment for workers in the right pane and sources tree. Also changes the Main thread icon to be document in the worker pane.
Differential Revision: https://phabricator.services.mozilla.com/D25121
--HG--
extra : moz-landing-system : lando
- Reads the value for the letter-spacing CSS property and shows it in the Font Editor. When it is default, show the "normal" identifier. As soon as the user tries to edit it using the value slider, switch to an em-based value.
- Tweaks the unit conversion method to support letter-spacing: using correct reference node for em units, returning high-precision results even for pixels (allow sub-pixel precision)
Differential Revision: https://phabricator.services.mozilla.com/D25087
--HG--
extra : moz-landing-system : lando
Depends on D25061
Two motivations to support the old routes:
- we have some links inside Firefox (application panel, about:addons, Developer Menu) that link to about:debugging. With this fix we avoid updating the links with code that depends on the value of the preference. We will fully update the links once the old aboutdebugging codebase is removed.
- there are some external pages that refer to about:debugging#workers or about:debugging#addons (did a quick google search). not a lot of them but this will also allow to keep supporting them
Differential Revision: https://phabricator.services.mozilla.com/D25062
--HG--
extra : moz-landing-system : lando
Moved tab context menu out of browser.dtd to browser.xul except for sendPageToDevice, sendLinkToDevice, moveTabOptions, moveSelectedTabOptions, undoCloseTab. Not sure if tabbrowser.js and tabbrowser.xul are working as intended.
Differential Revision: https://phabricator.services.mozilla.com/D19312
--HG--
extra : moz-landing-system : lando
If there's at least 2 content blocking messages displayed
for a given page navigation, we display a warning group
containing the messages, collapsed by default.
This means we need to move or insert those warning messages
at the right position in visibleMessages, either when they're
added, or when we expand a group.
Two mochitest are added to make sure this works as expected,
one for generic warningGroup features (expanding, group per
navigation session, …), and another one specifically for
content blocking warning group, where we check that every
type of content blocking message can be grouped.
The grouping won't occur unless the groupWarnings preferences
is on.
Differential Revision: https://phabricator.services.mozilla.com/D23552
--HG--
extra : moz-landing-system : lando
This component will be used to render warning groups messages.
We also add a `inWarningGroup` prop to the `Message` component
so warnings that will be displayed in such warningGroup can
be styled differently (no warning icon, a different color for
the indent).
Add some utils functions and constants to check if a message
should be a warning group.
Differential Revision: https://phabricator.services.mozilla.com/D23551
--HG--
extra : moz-landing-system : lando
This will be used to enable groups of warning messages (Tracking Protection,
CSP, CORS, …).
Differential Revision: https://phabricator.services.mozilla.com/D23550
--HG--
extra : moz-landing-system : lando
If there's at least 2 content blocking messages displayed
for a given page navigation, we display a warning group
containing the messages, collapsed by default.
This means we need to move or insert those warning messages
at the right position in visibleMessages, either when they're
added, or when we expand a group.
Two mochitest are added to make sure this works as expected,
one for generic warningGroup features (expanding, group per
navigation session, …), and another one specifically for
content blocking warning group, where we check that every
type of content blocking message can be grouped.
The grouping won't occur unless the groupWarnings preferences
is on.
Differential Revision: https://phabricator.services.mozilla.com/D23552
--HG--
extra : moz-landing-system : lando
This component will be used to render warning groups messages.
We also add a `inWarningGroup` prop to the `Message` component
so warnings that will be displayed in such warningGroup can
be styled differently (no warning icon, a different color for
the indent).
Add some utils functions and constants to check if a message
should be a warning group.
Differential Revision: https://phabricator.services.mozilla.com/D23551
--HG--
extra : moz-landing-system : lando
This will be used to enable groups of warning messages (Tracking Protection,
CSP, CORS, …).
Differential Revision: https://phabricator.services.mozilla.com/D23550
--HG--
extra : moz-landing-system : lando
I agree that we should remove PostCSS but since we have contributors moving to MC, I want to get this fixed ASAP.
Differential Revision: https://phabricator.services.mozilla.com/D25258
--HG--
extra : moz-landing-system : lando
Removes Node.js as an option for library detection to prevent issues in console.
Differential Revision: https://phabricator.services.mozilla.com/D25236
--HG--
extra : moz-landing-system : lando
The client close() method is not used anywhere. Individual callers should be responsible for closing opened sockets if needed.
Removing this method and the _sockets array, we no longer leak strings when calling adb.updateRuntimes()
Differential Revision: https://phabricator.services.mozilla.com/D25213
--HG--
extra : moz-landing-system : lando
Pass on column from props.onViewSourceInDebugger (///devtools/client/shared/components/reps/reps.js:6844//) to
//devtools/client/webconsole/webconsole-wrapper.js:267// as **frame.column**
Differential Revision: https://phabricator.services.mozilla.com/D22372
--HG--
extra : moz-landing-system : lando
