Adds a new devtools tooltip type in the inspector used to edit
css filters. The widget displayed in the tooltip allows to add,
edit, remove, and re-order filters.
Changes made inside the tooltip are applied to the filter
property in the rule-view.
--HG--
extra : rebase_source : a38ce7108bfa4e035892c3c3d89098dc1b2b0052
extra : histedit_source : ff309c03f920359df61e139731f8f57cf55a1545
This makes the inspector search input show suggestions for nodes in all documents in
the content page. Selecting a suggestion also now selects the corresponding nodes
even when they are inside nested frames.
--HG--
extra : rebase_source : e7d3ac809ea8f223acfb5d04dd72a9e6a292796d
Instead of only refreshing the list of animation widgets when the animations
controller emits an event, also refresh it once after the initialization is
done. This is useful to avoid missing animations that are already applied to
the default inspector selection.
--HG--
extra : rebase_source : f64cbdd4ad68c3cd733a86b7e2729005614a7049
This adds a new icon, next to the searchbox (like in the debugger) to expand
or collapse the sidebar panel in the inspector.
The state is *not* persisted yet when the toolbox is closed.
The button is hidden when the toolbox host switches to 'side'.
--HG--
extra : transplant_source : %D0%09%C2%0E%23%94%B0%A9Ym%BF%1B%60%3C%A5%D6D%C3%92%DE
(Re-land after backout)
The animation-controler was in charge of getting new animation players and refreshing
the UI when done. This is still the case, but it now listens for mutation events from
the actor too, and when they happen, it simply asks the ui to refresh again.
Also, animations with playState "finished" that remain in the animation inspector panel
can now be played again.
--HG--
extra : rebase_source : 309a167b2218c6fc586c64977896a4715bd5a1d5
This adds a playbackRate <select> dropdown next to the list of other playback
control buttons (play/pause, rw, fwd).
The list shows presets, unless the current rate isn't part of these presets
in which case it also shows this rate in the list.
The widget was created as a reusable component with a simple API, like the
PlayerMetaDataHeader.
--HG--
extra : rebase_source : d050fdaa4565a7b51b179ecd08a36b79be2275f1
The toolbar class was making the whole background of the animation panel
be grey, unlike the other inspector side-bar panels.
Also removed the unnecessary right-border on the global play/pause button.
This changes a few animationinspector tests by making them wait until the expected animation
state is reached rather than just waiting for the next animation auto-refresh update, which
might, in some cases, not be enough.
This is a re-landing of bug 1134500 and bug 1149711.
Backed out changeset 527c548ff03c (bug 1149711)
Backed out changeset 2fe22ffef154 (bug 1120833)
Backed out changeset 501fa7c170ed (bug 1120833)
CLOSED TREE
Wait for the playState to reach the expected state rather than just waiting for the next auto
refresh of the AnimationPlayerActor.
--HG--
extra : rebase_source : 4efede2ea007fed766e9714e2aff5399170d4b57
The toolbar class was making the whole background of the animation panel
be grey, unlike the other inspector side-bar panels.
Also removed the unnecessary right-border on the global play/pause button.
--HG--
extra : rebase_source : 7b2311bf06294e7e334aeee556d564809d4afcfe
On particularly slow test environments, it might not be enough to wait for the next
AnimationPlayerActor state update.
I introduced a helper function that makes it possible for tests to wait for state
updates until the animation state reaches the expected value. In most cases, we use
it to wait until an animation reaches a given playState (paused, running, finished).
--HG--
extra : rebase_source : 791da93c00b4eaffe8c31001fc9a2cdec4dc7e4c
The animation-controler was in charge of getting new animation players and refreshing
the UI when done. This is still the case, but it now listens for mutation events from
the actor too, and when they happen, it simply asks the ui to refresh again.
Also, animations with playState "finished" that remain in the animation inspector panel
can now be played again.
--HG--
extra : rebase_source : 8fe6e245ec04bfe399166e343b888b6ce3ca0ef1
This makes the AnimationsActor listen for animation mutations after each
call to getAnimationPlayersForNode on the code that was passed in.
Whenever animations are added or removed, an event is sent to the front
with the list of changes.
The server doesn't know when the client doesn't require updates for the
current node anymore, so it exposes a new method for this.
Note that removed events for finished aniations are skipped, because the
corresponding animations can still be seeked/resumed, so we want the
AnimationPlayerActor to be preserved.
--HG--
extra : rebase_source : 4a9be4695261d65a2f032117af9fce985f5c0378
The AnimationPlayerFront needs to emit events when its auto-refresh
mode is enabled, whenever the state changes. Until now, it was doing
so with EventEmitter.
But because decorating the class with EventEmitter adds on/once/off
functions to the instance, it ends up hiding the on/once/off functions
that were already there because the class extends addon sdk EventTarget.
--HG--
extra : rebase_source : 16c097df7b579b980f710ffbd98fe3d01a6fbc76
Instead of waiting for the next auto-refresh event only (which could be a
response to an older request, therefore not having the expected state yet),
wait until the state changes to what we expect in the test.
This means that if the play/pause button doesn't work anymore, then the test
will timeout, but at least it won't intermittently fail as it was doing until
now.
--HG--
extra : rebase_source : 75b7ffd38cc9fe83bb938c28109d12c57fbf3294
helper_outerhtml_test_runner.js was accessing DOM nodes directly in content (via
CPOWs) to check their outerHTML.
This change adds outerHTML, innerHTML and textContent to the common
devtools:test:getDomElementInfo frame-script message listener so that the test
can get it there instead.
--HG--
extra : rebase_source : 35b1994c6235475f2b295a201f464a5ff50a5555
The common assertAttributes helper test function used to access DOM nodes in the
content page directly (CPOW). It now becomes an async function that goes through
a frame-script to retrieve the list of attributes for a node, given its selector.
All tests were passing with this change but one: browser_markupview_tag_edit_06.js
This one was checking camelcase attribute names while the actual names on the
node were lowercased by the browser. The way we were asserting attributes before
didn't care about the case. Now it does.
--HG--
extra : rebase_source : 280a00192ce0d530594a1baed5ff58c763365029
Making use of the devtools test frame-script to set the test node's attributes instead of
using a CPOW.
--HG--
extra : rebase_source : 34533fb589ec40fde60be6275b3da99d3e58a2f5
This change updates the browser_markupview_tag_edit_03.js test by making use of the
getDomElementInfo message listener to retrieve information about the tested nodes
without having to go through CPOWs.
--HG--
extra : rebase_source : 550d6fdf0baa4557be024e42de1e9b7f03652b0b
extra : histedit_source : 65f0bdbdb1b315783b101eb54b2f405c03a1f79d
This change loads the devtools common frame-script-utils.js frame-script in the browser message
manager when a new test tab is opened by a test, and it adds a new getDomElementInfo message
listener useful for many tests to retrieve data about a node without having to go through a
CPOW.
--HG--
extra : rebase_source : 7783609faa96ba9a321156f781101244acd9ae2d
extra : histedit_source : 171b976aa669f59342d31dbe278cda3769988c2b%2C5c1851a0090c961e04c26ecdc167b4c4b965c73f
