Depends on D21007
Adds a Copy All Changes button to the toolbar of the Changes panel.
When pressed, this builds a stylesheet out of the changes for all sources tracked (stylesheets, element styles, etc)
The output format is the same as the now defunct Bug 1524548 with the added code comment as separator between the sources.
Differential Revision: https://phabricator.services.mozilla.com/D21008
--HG--
extra : moz-landing-system : lando
Remove the Copy All and Copy All Changes context menu options form the Changes panel context menu. As decided by PM & UX, they will be replaced with a single Copy All Changes button in the toolbar (part 2 of this series).
Differential Revision: https://phabricator.services.mozilla.com/D21007
--HG--
extra : moz-landing-system : lando
Adds a button that shows up when hovering selectors in the Changes panel.
When clicked, it invokes the same Copy Rule behavior implemented for the context menu: copies the full content of the rule with changes applied.
The added/changed CSS class names use BEM notation. I intend to refactor the Changes panel stylesheet to BEM in a follow-up patch.
Differential Revision: https://phabricator.services.mozilla.com/D20808
--HG--
extra : moz-landing-system : lando
Depends on D20808
Adds a Copy All Changes button to the toolbar of the Changes panel.
When pressed, this builds a stylesheet out of the changes for all sources tracked (stylesheets, element styles, etc)
The output format is the same as the now defunct Bug 1524548 with the added code comment as separator between the sources.
Differential Revision: https://phabricator.services.mozilla.com/D21008
--HG--
extra : moz-landing-system : lando
Remove the Copy All and Copy All Changes context menu options form the Changes panel context menu. As decided by PM & UX, they will be replaced with a single Copy All Changes button in the toolbar (part 2 of this series).
Differential Revision: https://phabricator.services.mozilla.com/D21007
--HG--
extra : moz-landing-system : lando
Adds a button that shows up when hovering selectors in the Changes panel.
When clicked, it invokes the same Copy Rule behavior implemented for the context menu: copies the full content of the rule with changes applied.
The added/changed CSS class names use BEM notation. I intend to refactor the Changes panel stylesheet to BEM in a follow-up patch.
Differential Revision: https://phabricator.services.mozilla.com/D20808
--HG--
extra : moz-landing-system : lando
This patch allows hovering over box-model values and scrolling to their source CSS rule while pressing down the shift-key,
Differential Revision: https://phabricator.services.mozilla.com/D18772
--HG--
extra : moz-landing-system : lando
When removing all declarations from a rule via the Rule view, the authoredText value ends up as an empty string.
This patch ensures that the fallback cssText is not used in that case because that accidentally restores the whole declaration block when re-parsing the text of the rule.
Differential Revision: https://phabricator.services.mozilla.com/D14753
--HG--
extra : moz-landing-system : lando
Removed the 'filterBarVisible' required prop from the FilterBar component, which is no longer needed after the changes in Bug 1523861.
Differential Revision: https://phabricator.services.mozilla.com/D20948
--HG--
extra : moz-landing-system : lando
When removing all declarations from a rule via the Rule view, the authoredText value ends up as an empty string.
This patch ensures that the fallback cssText is not used in that case because that accidentally restores the whole declaration block when re-parsing the text of the rule.
Differential Revision: https://phabricator.services.mozilla.com/D14753
--HG--
extra : moz-landing-system : lando
This already matches the behaviour for official builds (opt and debug in automation).
Tests don't expect event bubbles from chrome event listeners in the inspector on unprivileged test pages.
Differential Revision: https://phabricator.services.mozilla.com/D20887
--HG--
extra : moz-landing-system : lando
A JSScript can be explicitly cloned and applied to a new realm. When this is done within the same compartment
as the original JSScript, it maintains its reference to the original ScriptSourceObject. This can lead to the
potentially surprising fact that using Debugger.findScripts({ source }) can return multiple Debugger.Script
objects representing the same function, but in multiple realms.
When we query for breakpoints in a given source, we want to take the first column breakpoint on a given line,
but that needs to apply to all potential instances of the Debugger.Script for that location, not just the first one.
Differential Revision: https://phabricator.services.mozilla.com/D20431
--HG--
extra : moz-landing-system : lando
It's possible that CSSPseudoElement will grow a 'ownerDocument' member in future
so instead we should test for '.element'. We could also test for '.type' but it
seems more likely that Element will grow a 'type' member than an 'element'
member.
Ideally we should really test if the target is an instanceof CSSPseudoElement
but unfortunately the window() getter it itself defined in terms of the node()
getter (which calls isPseudoElement) so we'd end up with unbounded recursion
unless we restructure these getters.
Differential Revision: https://phabricator.services.mozilla.com/D20428
--HG--
extra : moz-landing-system : lando
shindli
Daisuke Akatsuka
Andrea Marchesini
Razvan Caliman
arthur.iakab
Jason Laster
Micah Tigley
Julian Descottes
Oana Pop Rus
Martin Koroknay
Dorel Luca
Jonathan Kingston
Razvan Maries
ui.manish
Matthew Noorenberghe
Coroiu Cristina
Mats Palmgren
Michael Ratcliffe
Gabriel Luong
Brian Hackett
Logan Smyth
Rainier G
Brian Birtles
Noemi Erli
Jason Laster
Yura Zenevich