1625401 - Button for removing breakpoints/expressions remains displayed if click+drag away action is issued

Status: NEW

(DevTools :: Debugger, defect, P3)

Description

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This is a follow up for bug 1585313

STR

1. Open DevTools and select the Debugger tab
2. Create set of JS/DOM/XHR Breakpoints and set of Watch expressions (at least two in each set)
3. Hover over the x button (in any of those sets)
4. Click and hold the mouse button dragging the mouse over another one;
5. Release the mouse button.

ER:
The x button for first item is not displayed anymore;

AR:
both x buttons are displayed;
first x button is displayed until another click is issued.

Honza

Comment 1

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Anyone interested in fixing this bug can take an inspiration from this patch:
https://phabricator.services.mozilla.com/D68329

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

The bug probably doesn't exist in MacOS
Can someone verify?

Honza

Comment 3

[Kriyszig]

I would like to work on this.
Turns out the close button is a shared component in the debugger and this behavior is present in multiple places aside from the breakpoints panel within the Debugger panel.

Comment 4

[Jason Laster [:jlast]]

Go for it Kriyszig

Comment 5

[Kriyszig]

Thank you @jlast

Comment 6

[Kriyszig]

Attachment: Bug 1625401 - Remove CSS that makes the close button persist when click and drag is performed in Debugger r=jlast,yzen

A click and drag focuses the element activationg the CSS properties
within the :focus. This makes the buttons persist when the
user performs click and drag leading to display of multiple close
buttons which is confusing to user.
Removing the :hover doesn't affect the ultimate behavior as the
close button signifies the last click before the element goes out
of view for the user. Thus this change shouldn't make a difference
to the intended user experience.
Note: This bug might not be reproducible on MacOS based on the
comments on review in D68329

Comment 7

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months.
:bomsy, could you have a look please?
For more information, please visit auto_nag documentation.