Adding feature to netmonitor for resizing of columns. In this patch the functionality is hidden behind the pref devtools.netmonitor.features.resizeColumns. This feature is currently turned off - false.
Differential Revision: https://phabricator.services.mozilla.com/D22719
--HG--
extra : moz-landing-system : lando
Before this change clicking on Storage Type use to show table headers from previous selection. Now clicking on Storage Type will reset table headers also in case empty table headers will get cleared.
Differential Revision: https://phabricator.services.mozilla.com/D22327
--HG--
extra : moz-landing-system : lando
When a message was repeated, the bubble would appear and
slightly increase the message size (by 1px), making it
lose its bottom-anchoring. Then, if a new message came,
the console won't automatically scroll anymore.
This patch modifies the repeat bubble CSS so it doesn't
impact the message height, and add a test case in the
test which asserts the scroll to bottom feature.
Differential Revision: https://phabricator.services.mozilla.com/D22672
--HG--
extra : moz-landing-system : lando
For consistency with other parts of DevTools, the Network monitor toolbar (or toolbars, when splitted in 2) should be 28px high excluding borders.
Currently it’s 29px, 1px taller than the toolbox's tab bar, and 1px taller than the Console’s toolbar.
Differential Revision: https://phabricator.services.mozilla.com/D22430
--HG--
extra : moz-landing-system : lando
This changes the colors of the odd table cells and the hover state in rows in the Network tab in DevTools.
I have updated the //--table-zebra-background// in **variables.css** and inserted a new one, which is //--table-selection-background-hover//.
I have created the new variable, in order to prevent it affecting other table colors.
Differential Revision: https://phabricator.services.mozilla.com/D21777
--HG--
extra : moz-landing-system : lando
Changed the way we to access contents of `.CodeMirror`, by using `CodeMirror.getValue()` instead of `.textContent`
Differential Revision: https://phabricator.services.mozilla.com/D22079
--HG--
extra : moz-landing-system : lando
The only fishy bit is the animation stuff. In particular, there are two places
where we just mint the revert behavior:
* When serializing web-animations keyframes (the custom properties stuff in
declaration_block.rs). That codepath is already not sound and I wanted to
get rid of it in bug 1501530, but what do I know.
* When getting an animation value from a property declaration. At that point
we no longer have the CSS rules that apply to the element to compute the
right revert value handy. It'd also use the wrong style anyway, I think,
given the way StyleBuilder::for_animation works.
We _could_ probably get them out of somewhere, but it seems like a whole lot
of code reinventing the wheel which is probably not useful, and that Blink
and WebKit just cannot implement either since they don't have a rule tree,
so it just doesn't seem worth the churn.
The custom properties code looks a bit different in order to minimize hash
lookups in the common case. FWIW, `revert` for custom properties doesn't seem
very useful either, but oh well.
Differential Revision: https://phabricator.services.mozilla.com/D21877
--HG--
extra : moz-landing-system : lando
Take into account new service worker implementation to decide if workers can be debugged
Differential Revision: https://phabricator.services.mozilla.com/D20677
--HG--
extra : moz-landing-system : lando
Similar to bug 1528654, we currently bail out too early and don't process all of the correct scripts when adding breakpoints.
Differential Revision: https://phabricator.services.mozilla.com/D22355
--HG--
extra : moz-landing-system : lando
I don't understand how the test ever worked. I think the idea was that each
operation would result in changes to the prefs, because those prefs are the
source of truth for the recent-files list. However, I don't understand why some
tests would not trigger multiple observer callbacks, which should have been a
huge mess.
The new code doesn't observe the prefs at all. Where possible, it waits for an
appropriate promise; in other places it uses `setTimeout()` to wait for the
next tick, relying on the Scratchpad implementation to be done reacting by
then.
Since the original code was event-driven, most tests were split across two
functions. Each test function had the bottom half of one test and the top half
of the next test. The new code uses async/await and can therefore at least
group related functionality into single cohesive test functions. But those test
functions aren't as independent as they look -- most of them still depend on
previous tests to set up the expected starting state.
Differential Revision: https://phabricator.services.mozilla.com/D20759
--HG--
extra : moz-landing-system : lando
Tests can use the promise to avoid racing on the text being available and the
UI ready for interaction.
Differential Revision: https://phabricator.services.mozilla.com/D20758
--HG--
extra : moz-landing-system : lando
Jason Laster
Csoregi Natalia
Mike Conley
Nicolas Chevobbe
Laphets
lenka
Oana Pop Rus
ivan
avi.mathur
lloan
Narcis Beleuzu
Edwin Gao
arthur.iakab
Ciure Andrei
Mellina Yonashiro
Michael Ratcliffe
Hemakshi Sachdev
Micah Tigley
Emilio Cobos Álvarez
Helena Moreno
sole
Dorel Luca
ravefalcon92
Daisuke Akatsuka
Jason Orendorff
Brian Hackett