Closed Bug 2019067 Opened 6 months ago Closed 4 months ago

Zoom level of devtools can affect expand on hover rect for vertical tabs

Categories

(Firefox :: Sidebar, defect, P2)

defect

Tracking

()

RESOLVED FIXED
152 Branch
Tracking Status
firefox152 --- fixed

People

(Reporter: mconley, Assigned: sfoster)

References

Details

(Whiteboard: [fidefe-sidebar])

Attachments

(2 files)

STR:

  1. Enable vertical tabs, with expand on hover enabled to true
  2. On any page, open up browser devtools (not the Browser Toolbox, the in-page developer tools), via F12
  3. With the devtools focused (perhaps by clicking on the text area in the console), increase the zoom level to maximum by holding Ctrl and + (or Cmd and + on macOS)
  4. With the devtools zoomed, move the mouse cursor over top of the inspect button in the top left of the devtools

ER:

The vertical tabs should only expand when the vertical tab strip is hovered.

AR:

With a high enough zoom level, just passing over the inspect button's halfway point seems to be enough to trigger it.

See attached video.

The workaround is to reset the zoom level of the devtools to the default with Ctrl / Cmd + 0

Hi Nicholas. We wondering if you've seen similar issues or have any ideas on a fix for this? Thanks!

Severity: -- → S3
Flags: needinfo?(nchevobbe)
Priority: -- → P2
Whiteboard: [fidefe-sidebar]

(In reply to Nikki Sharpley (:nikkis) (she/her) from comment #2)

Hi Nicholas. We wondering if you've seen similar issues or have any ideas on a fix for this? Thanks!

I thought we had something similar in the past, but I can't find a bug that would describe the same situation :/

Flags: needinfo?(nchevobbe)
Component: Tabbed Browser → Sidebar
Priority: P2 → P3
Priority: P3 → P2

I'll take a look into this.

Assignee: nobody → sfoster
Status: NEW → ASSIGNED

It looks like the event.screenX and event.screenY values we get in handleEvent are pre-scaled using the target's devicePixelRatio. In this case, although the currentTarget is the ChromeWindow, the event.target is a devtools inspector element so everything gets scaled by its dpr which is 4 (max zoom level). At this point, subtracting window.mozInnerScreenX doesn't make any sense - these are different coordinate spaces.

Pushed by sfoster@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/52f980476bad https://hg.mozilla.org/integration/autoland/rev/2c34f83e5719 Re-scale coordinates in MousePosTracker to account for a different target's devicePixelRatio. r=emilio,frontend-codestyle-reviewers
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch
QA Whiteboard: [qa-triage-done-c153/b152]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: