Closed Bug 1543129 Opened 2 years ago Closed 2 years ago

Most customizable items (looks like all API-based widgets) go AWOL after using Forget button


(Firefox :: Toolbars and Customization, defect, P1)




Firefox 68
Tracking Status
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- verified


(Reporter: mberlinger, Assigned: Gijs)



(1 file)

Affected versions

  • 68.0a1(2019-04-09)
  • 67.0b9
  • 66.0.2

Affected platforms

  • mac OS 10.13.6
  • Windows 7x64
  • Windows 10x64
  • Ubuntu 18.04x64

Steps to reproduce

  1. Launch Firefox
  2. Go to customize
  3. Move all items in overflow menu
  4. Click "Restore defaults" button
  5. Drag "Forget" item in toolbar
  6. Click the Forget item then the "Forget" button
  7. Go to customize

Expected result

  • All items are displayed.

Actual result

  • Just 6 items are displayed

Regression range

  • This is not a recent regression since I was able to reproduce it on Firefox 65.0. I'll investigate asap.

Additional notes

  • After refreshing the Firefox all items are displayed

A regression window would be very helpful here.

Assignee: nobody → gijskruitbosch+bugs
Flags: needinfo?(maria.berlinger)
Priority: -- → P1
Summary: Customize items aren't all displayed after using Forget button → Most customizable items (looks like all API-based widgets) go AWOL after using Forget button

It looks like just moving 1 API-based widget, like the zoom controls, instead of all of them, and otherwise following the same steps as comment #0, makes that specific widget disappear.

Also, just closing the initial window and opening another one does the same job (on mac, where the process stays live in that case).

This issue is not a regression since I was able to reproduce it on Firefox from 2014-09-29 when the "Forget" button was first implemented.

Flags: needinfo?(maria.berlinger)

This is caused by ignoring widgets with a currentArea defined, and the fact that currentArea is not updated for API-based widgets when resetting. We don't normally notice this when widgets have already been defined in the same window, but this means a simpler set of STR is:

  1. open firefox
  2. open customize mode
  3. move developer button to a toolbar or the panel
  4. click 'restore defaults'
  5. close customize mode
  6. open a new window
  7. open customize mode in the new window

developer button is present in customize mode

it isn't.

This is a bit of an edgecase and easy to workaround, and doesn't affect anything outside of customize mode, so I'm wontfixing for 67 because this code is... complex.

Pushed by
fix buttons disappearing in customize mode after using 'restore defaults', r=jaws
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 68
Flags: qe-verify+

This issue is verified fixed using Firefox 68.0b9 on the following OSes: Windows 10x64, Windows 7x64, Ubuntu 18.04x64, mac OS 10.13.6.

Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.