Closed Bug 1648060 Opened 3 months ago Closed 2 months ago

start-panel growth is not limited to available width

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(firefox80 fixed)

RESOLVED FIXED
Firefox 80
Tracking Status
firefox80 --- fixed

People

(Reporter: alexand.dominguez, Assigned: alexand.dominguez)

Details

Attachments

(2 files)

Attached video 0.mov

Description

If the Debugger's start-panel is dragged past the available width, the next time the end-panel is retracted, the start-panel will grow to occupy that width. Instead, the start-panel should be limited to the available width. A video of the bug is attached.

STR

  1. Expand the end-panel to its maximum width.
  2. Expand the start-panel past the maximum width the UI will allow, i.e., keep dragging to the right of the screen. At some point, let go. The start-panel has now been assigned a width larger than the space available to it.
  3. Drag the end-panel to decrease its width. As the end-panel retracts, the start-panel will grow to occupy its assigned width.

Expected

The start-panel's possible width should be limited by the available width of the UI.

I have added a helper method, calcStartPanelWidth(), to limit the start-panel on expansion.

Assignee: nobody → alexand.dominguez

We discussed this during the review for Bug 1599978, here's a link to that discussion: https://phabricator.services.mozilla.com/D73381#2347415

Fix is now ready.

Flags: needinfo?(dwalsh)
Flags: needinfo?(dwalsh) → needinfo?(hmanilla)
Flags: needinfo?(hmanilla)

The severity field is not set for this bug.
:loganfsmyth, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(loganfsmyth)
Severity: -- → S3
Flags: needinfo?(loganfsmyth)
Priority: -- → P3
Pushed by dwalsh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f65bc98a26f2
start-panel sidebar prevented from being dragged wider than the available width. r=davidwalsh,bomsy
Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 80
You need to log in before you can comment on or make changes to this bug.