Open Bug 1711891 Opened 4 months ago Updated 4 months ago

[New bookmark] Adding a new folder causes field to overlap scrolling bar in the Bookmarks Panel folder selector

Categories

(Firefox :: Bookmarks & History, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox88 --- disabled
firefox89 --- affected
firefox90 --- affected

People

(Reporter: clara.guerrero, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [proton-door-hangers])

Attachments

(1 file)

Attached video overlap.webm

Affected platforms:
Platforms: All

Preconditions
Set the following prefs in about:config

browser.proton.enabled = true
prompts.windowPromptSubDialog = true
prompts.contentPromptSubDialog = true
browser.proton.modals.enabled = true

Steps to reproduce

  1. Launch the Firefox browser
  2. Visit any website
  3. Click on bookmark icon
  4. Expand folder by clicking on down arrow
  5. Click on New folder option

Expected result
The field to input value should be properly displayed

Actual result
The field to input value is wrongly displayed and overlapping scrolling bar.

(In reply to Clara Guerrero from comment #0)

Preconditions
Set the following prefs in about:config

browser.proton.enabled = true
prompts.windowPromptSubDialog = true
prompts.contentPromptSubDialog = true
browser.proton.modals.enabled = true

With the steps below, I can reproduce without any of these prefs set, in Firefox from Jan 1st this year, so I don't think this is proton-related - I think it's always been an issue. So going to remove the proton tracking bugs. :-)

Steps to reproduce

  1. Launch the Firefox browser
  2. Visit any website
  3. Click on bookmark icon
  4. Expand folder by clicking on down arrow
  5. Click on New folder option
Component: Notifications and Alerts → Bookmarks & History
OS: Unspecified → All
Product: Toolkit → Firefox
Hardware: Unspecified → Desktop
See Also: → 1705180, 1708159
Whiteboard: [proton-cleanups]
Whiteboard: [proton-cleanups] → [proton-door-hangers]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.