Introduce `overflow-wrap: break-word` to CSS declarations in Rules view and Changes panel to prevent long strings from causing unwanted horizontal scroll
Differential Revision: https://phabricator.services.mozilla.com/D27120
--HG--
extra : moz-landing-system : lando
Depends on D26920
See Bug 1532993#c12 for the analysis. The extra rendering is due to a window resize that
seems to always happen on ASAN but not on other platforms.
Differential Revision: https://phabricator.services.mozilla.com/D27143
--HG--
extra : moz-landing-system : lando
Depends on D26900
Fixes the blank chart and load issues for the old perf panel in about:devtools-toolbox (or type=content)
Differential Revision: https://phabricator.services.mozilla.com/D26919
--HG--
extra : moz-landing-system : lando
Depends on D26899
This test would timeout with the fix in the previous patch
Differential Revision: https://phabricator.services.mozilla.com/D26900
--HG--
extra : moz-landing-system : lando
Follow up to 1524982. We started using the browserloader to load almost all perf panel files.
However we kept two async methods in the js file loaded by performance/index.xul, which defeated the purpose.
Differential Revision: https://phabricator.services.mozilla.com/D26899
--HG--
extra : moz-landing-system : lando
As we convert more chrome documents away from XUL we end up running
through two different paths in this function. These are going to be
filtered out in later checks anyway, so this change removes the early return.
Differential Revision: https://phabricator.services.mozilla.com/D26574
--HG--
extra : moz-landing-system : lando
Depends on D26900
Fixes the blank chart and load issues for the old perf panel in about:devtools-toolbox (or type=content)
Differential Revision: https://phabricator.services.mozilla.com/D26919
--HG--
extra : moz-landing-system : lando
Depends on D26899
This test would timeout with the fix in the previous patch
Differential Revision: https://phabricator.services.mozilla.com/D26900
--HG--
extra : moz-landing-system : lando
Follow up to 1524982. We started using the browserloader to load almost all perf panel files.
However we kept two async methods in the js file loaded by performance/index.xul, which defeated the purpose.
Differential Revision: https://phabricator.services.mozilla.com/D26899
--HG--
extra : moz-landing-system : lando
Depends on D26320
@miker: We are moving devtools iframes to use type=content, and win.top will no longer be available.
We could use another getter to get the topmost chrome window, but reading the code here, I thought that maybe using the toolbox window would be better.
Today if you open several toolboxes in different tabs of the same window, the events for the various toolboxes will be mixed together, because win.top is the same for all the toolboxes that live in the same window.
It might be better to use an object which is unique to the toolbox?
Differential Revision: https://phabricator.services.mozilla.com/D26324
--HG--
extra : moz-landing-system : lando
Depends on D26316
Instead of using a hardcoded iframe in toolbox-window.xul, reuse the same helper as for the other hosts.
Will facilitate switching to type="content".
Differential Revision: https://phabricator.services.mozilla.com/D26317
--HG--
extra : moz-landing-system : lando
Shared helper to create DevTools frames for side and bottom hosts.
Will make it easier to swap to type="content" in a single spot.
Differential Revision: https://phabricator.services.mozilla.com/D26316
--HG--
extra : moz-landing-system : lando
Any text enclosed between forward slashes is considered as a regex search. If the entered regex is invalid, a normal text search is performed.
Differential Revision: https://phabricator.services.mozilla.com/D26310
--HG--
extra : moz-landing-system : lando