Closed
Bug 1453246
Opened 7 years ago
Closed 7 years ago
If we hover the target element, we should not re-select it
Categories
(DevTools :: Inspector: Animations, defect, P3)
Tracking
(firefox-esr52 unaffected, firefox-esr60 unaffected, firefox60 unaffected, firefox61 disabled, firefox62 verified)
VERIFIED
FIXED
Firefox 62
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | unaffected |
firefox60 | --- | unaffected |
firefox61 | --- | disabled |
firefox62 | --- | verified |
People
(Reporter: gpalko, Assigned: daisuke)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
[Environment:]
Windows 8.1, Windows 10, Mac OSX 10.13.2
Nightly 61.0a1 2018-04-04
[Steps:]
1. Open Firefox Nightly and load https://rawgit.com/dadaa/3b73f847427025b51ba1ab7333013d0c/raw/77f3f0bb884875a179c3407f73bf8a8dd54751c9/doc_simple_animation.html.
2. Press F12.
3. Select Inspector.
4. Select Animation tab.
5. Select div.ball.multi from the Inspector
6. Hover over the nodes in Animation panel
[Actual Result:]
The element is re-selected on hover.
[Expected Result:]
Already selected elements should not be re-selected
Comment 1•7 years ago
|
||
Hi Gyula, I'm having a hard time understanding the bug here. The behavior seems to be the same to me with both the old and new animation inspector.
Flags: needinfo?(gyula.palko)
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Brian Birtles (:birtles) from comment #1)
> Hi Gyula, I'm having a hard time understanding the bug here. The behavior
> seems to be the same to me with both the old and new animation inspector.
Hi Brian,
This issue was pointed to us by Daisuke while we were discussing another issue. The point was that in case in which an element has multiple animations like the example in comment 0, the element should not be re selected because what results is a flicker effect with no additional gain.
This is probably more easily observed if, additionally to comment 0, you add an intermediary step before step 6 of clicking the target on an animation node:
5. Select div.ball.multi from the Inspector
5'. Click the target icon on any of the two animations.
6. Hover over the nodes in Animation panel
Flags: needinfo?(gyula.palko)
Comment 3•7 years ago
|
||
Oh, I see. It seems the new inspector allows locking the target element (whereas the old inspector does not appear to work in this case). Once an element is locked, we don't need to re-highlight it.
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 6•7 years ago
|
||
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=3ea2e5cc58335c2c2f85c61894a5fb2c864f7e18
Assignee: nobody → dakatsuka
Comment 7•7 years ago
|
||
mozreview-review |
Comment on attachment 8980182 [details]
Bug 1453246 - Part 1: Disable mouseover/mouseover if the target node already highlighted.
https://reviewboard.mozilla.org/r/246346/#review253132
::: devtools/client/inspector/animation/components/AnimationTarget.js:137
(Diff revision 1)
> defaultRep: ElementNode,
> mode: MODE.TINY,
> inspectIconTitle: getInspectorStr("inspector.nodePreview.highlightNodeLabel"),
> object: translateNodeFrontToGrip(nodeFront),
> onDOMNodeClick: () => this.select(),
> - onDOMNodeMouseOut: () => onHideBoxModelHighlighter(),
> + onDOMNodeMouseOut: isHighlighted ? null : () => onHideBoxModelHighlighter(),
I would prefer if we declared a handler function that did the following:
onDOMNodeMouseOver() {
if (!isHighlighted) {
onHideBoxModelHighlighter();
}
}
::: devtools/client/inspector/animation/components/AnimationTarget.js:138
(Diff revision 1)
> mode: MODE.TINY,
> inspectIconTitle: getInspectorStr("inspector.nodePreview.highlightNodeLabel"),
> object: translateNodeFrontToGrip(nodeFront),
> onDOMNodeClick: () => this.select(),
> - onDOMNodeMouseOut: () => onHideBoxModelHighlighter(),
> - onDOMNodeMouseOver: () => this.highlight(),
> + onDOMNodeMouseOut: isHighlighted ? null : () => onHideBoxModelHighlighter(),
> + onDOMNodeMouseOver: isHighlighted ? null : () => this.highlight(),
Same as above.
Attachment #8980182 -
Flags: review?(gl) → review+
Comment 8•7 years ago
|
||
mozreview-review |
Comment on attachment 8980183 [details]
Bug 1453246 - Part 2: Add test for avoiding double highlight.
https://reviewboard.mozilla.org/r/246348/#review253134
Attachment #8980183 -
Flags: review?(gl) → review+
Updated•7 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 11•7 years ago
|
||
Thanks Gabriel!
I have updated the patches.
Will land if the try was green.
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=cb527a959f14d8bc7a24962fb261304124360e2b
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 14•7 years ago
|
||
Sorry, I have updated again so as to avoid double highlight in case of clicking the icon after mouse over.
Could you check again?
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=4f0caff209662ac59220da4d6d29eefdf115362d
Flags: needinfo?(gl)
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 18•7 years ago
|
||
Rebased the patches.
Will land if the try was green.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b5321ba1a4fd7ac7b5b4435953384b64f65114d3
Comment 19•7 years ago
|
||
Pushed by dakatsuka@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1c0e5d523456
Part 1: Disable mouseover/mouseover if the target node already highlighted. r=gl
https://hg.mozilla.org/integration/autoland/rev/2f2884150d18
Part 2: Add test for avoiding double highlight. r=gl
Comment 20•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1c0e5d523456
https://hg.mozilla.org/mozilla-central/rev/2f2884150d18
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 62
Updated•7 years ago
|
Updated•7 years ago
|
Product: Firefox → DevTools
Reporter | ||
Comment 21•7 years ago
|
||
Verified as fixed on Nightly 62.0a1(20180618220118) on Win10, MacOS 10.12 and Ubuntu 16.04
You need to log in
before you can comment on or make changes to this bug.
Description
•