Depends on D20195
This series of patches depends on the patch from [Bug 1525238](https://bugzilla.mozilla.org/show_bug.cgi?id=1525238)
- adds method to identify a CSS Rule actor by id
- adds context menu option to the Changes panel to allow copying the rule's authored text to the clipboard
Differential Revision: https://phabricator.services.mozilla.com/D20196
--HG--
extra : moz-landing-system : lando
This series of patches depends on the patch from [Bug 1525238](https://bugzilla.mozilla.org/show_bug.cgi?id=1525238)
This patch adds a new method to the StyleRuleActor on the server to expose the full text content of a CSS rule over the protocol to the client. This means exposing the CSS rule's authored text including comments and any nested rules if the target rule is an ancestor rule, like @media or @supports.
There's minor refactoring to include additional rule types for which StyleRuleActors will be created: @supports, @media, @keyframes. These are not explicitly rendered in the Rule view and shouldn't impact it. The Rule view filters for CSS Style Rules, element inline style and has special handling for keyframe at-rules.
Differential Revision: https://phabricator.services.mozilla.com/D20195
--HG--
extra : moz-landing-system : lando
Will ask for r? from janerik once product has approved the data collected here.
Differential Revision: https://phabricator.services.mozilla.com/D19529
--HG--
extra : moz-landing-system : lando
tests; r=ochameau
this migrates the proxy to the new webconsole front events. This resulted in a number of
test failures once the migration was finished, and those were fixed
Differential Revision: https://phabricator.services.mozilla.com/D18834
--HG--
extra : moz-landing-system : lando
this patch introduces events for the webconsoleFront -- not all of them are being listened
to by their subscribers yet, but this is the bulk of the effort to move events to Protocol.js
Differential Revision: https://phabricator.services.mozilla.com/D18832
--HG--
extra : moz-landing-system : lando
initial move of the webconsoleClient to a front. Events do not work yet, but methods do.
Differential Revision: https://phabricator.services.mozilla.com/D18829
--HG--
extra : moz-landing-system : lando
The file and its dependencies are pretty large and can take
a while to load. Since some consumers might not need those function,
loading them lazily looks like a good move.
Differential Revision: https://phabricator.services.mozilla.com/D20147
--HG--
extra : moz-landing-system : lando
If the cssProperties config wasn't provided, the Editor
was loading getClientCssProperties, which loads properties-db
which is quite large.
Since the Style Editor is providing a cssProperties config,
this was done for all the other consumers, none of them
actually having any use of it.
We remove this default behaviour which allows us to speed
up panel/source opening quite significantly.
Differential Revision: https://phabricator.services.mozilla.com/D20305
--HG--
extra : moz-landing-system : lando
@daisuke I would like to share this preliminary work with you.
I want to move this to a dedicated component anyway, but most importantly this will reduce merge conflicts between our 2 bugs.
I can land that and leave-open while I continue to work on the actual UX implementation?
Depends on D20398
Differential Revision: https://phabricator.services.mozilla.com/D20399
--HG--
rename : devtools/client/aboutdebugging-new/src/components/RuntimePage.css => devtools/client/aboutdebugging-new/src/components/RuntimeActions.css
rename : devtools/client/aboutdebugging-new/src/components/RuntimePage.js => devtools/client/aboutdebugging-new/src/components/RuntimeActions.js
extra : moz-landing-system : lando
