Closed Bug 1656035 Opened 1 year ago Closed 1 year ago

Stop directory root header from breaking on to multiple lines

Categories

(DevTools :: Debugger, enhancement, P3)

78 Branch
enhancement

Tracking

(firefox81 fixed)

RESOLVED FIXED
81 Branch
Tracking Status
firefox81 --- fixed

People

(Reporter: kyleknaggs, Assigned: kyleknaggs)

Details

Attachments

(2 files, 1 obsolete file)

Attached video 20200727_directoryRootHeader.mov (obsolete) —

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36

Steps to reproduce:

  1. Visit http://todomvc.com/examples/jquery/#/all and open the Debugger.
  2. Right-click on any directory or thread in the Sources tab and select "Set Directory Root".
  3. Drag the right edge of the Primary pane to the left until it goes past the point at which the directory root header used to end before you began dragging the edge of the pane.

Actual results:

The directory root header breaks on to a second line.

Expected results:

The directory root header should behave in a manner that is consistent with the other items in the Sources tab. This means that instead of breaking on to a second line, the directory root header should continue to occupy a single line while the text that extends beyond the edge of the pane should be hidden.

Attachment #9166876 - Attachment is obsolete: true

Before this change whenever the directory root header extends to the edge of the Primary pane a flex-wrap CSS rule in the .sources-clear-root selector breaks the directory root header text on to multiple lines. This patch removes this rule and fixes this bug.

Assignee: nobody → kyleknaggs
Pushed by dwalsh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b97a46258d11
Remove CSS rule that wraps directory root header on to multiple lines r=davidwalsh
Severity: -- → S3
Type: defect → enhancement
Priority: -- → P3
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.