762011 - [highlighter] Node operation bar displayed but not accessible for on mouse hover elements

Status: RESOLVED INVALID

(DevTools :: Inspector, defect)

Description

[Virgil Dicu [:virgil] [QA]]

STR:

1. Visit addons.mozilla.org
2. Right click-select Inspect
3. Hover any of the featured extensions.
4. Inspect the "Add to Firefox" button.

Actual result: node operations bar is displayed in the upper left corner.
Firefox flickers when selecting the add-on from step 3 (another node operations bar is displayed, when hovering it the bar returns to its initial position-upper left corner)

Across platforms, including Firefox Nightly since pseudo class lock.

Comment 1

[Paul Rouget [:paul]]

This is an interesting problem.

This is what happen: the element is visible only if it (or its container) is :hover. When locked, we still see it. But if we over the infobar, or anything it disappear. So the infobar is moved to the top left corner. This is the expected behavior.

If we over the infobar, the element is hidden, so the infobar move the to top. So we over the container again, and we see the element, so the infobar comes back. But then, we over the infobar, and… etc -> flicker.

Very bad experience.

What if, when we lock a node, we:
1) make the veil not-click-through
2) force the pseudo-class :hover

Comment 2

[Rob Campbell [:rc] (:robcee)]

Interesting problem.

I don't think we can force :hover on lock. Users will want to be able to see both states and locking down the veil and the hover state on first inspection feels harsh. We *could* lock the veil when a user selects :hover from the pseudo-class lock control, however. That might make sense.

The inspector is technically working as-designed here. A user can work around the problem by finding the node in the hierarchy that requires :hover-ing, and, while locked, select that from the node menu to lock it in place. Using the breadcrumbs, the user can then navigate to the install button and select it.

not ideal.

Maybe make :hover-on-lock an option on the gear menu?

Comment 3

[Paul Rouget [:paul]]

Similar problem here: bug 779605

Comment 4

[Heather Arthur [:harth]]

If :hover is by far the most common cause of the node disappearing, then maybe we could force :hover on lock only in the cases where the node disappears.

If we did that, it would be good to show a message saying that we forced :hover because the node disappeared, with instructions on how to remove the :hover.

Comment 5

[Paul Rouget [:paul]]

We could just lock :hover when the mouse enters the infobar, and unlock when it leaves the infobar.

Comment 6

[Paul Rouget [:paul]]

Bug triage, filter on PINKISBEAUTIFUL

Comment 7

[Gabriel Luong [:gl] (ΦωΦ)]

Marking as invalid since the node operation bar no longer exists