Open Bug 1960940 Opened 1 year ago Updated 1 year ago

Delayed display of menuitem(`Profiles`) in menubar invites misclicked items.

Categories

(Toolkit :: Startup and Profile System, defect, P3)

Product:
Toolkit
Component:
Startup and Profile System
Platform:
Desktop
Windows 11
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr128 --- unaffected
firefox137 --- wontfix
firefox138 --- disabled
firefox139 --- disabled
firefox140 --- disabled

People

(Reporter: alice0775, Unassigned)

References

(Regression)

Details

(Keywords: nightly-community, regression, ux-error-prevention, Whiteboard: [fidefe-profile-management])

STR

  1. Enable menu bar
  2. Restart browser
  3. Click on Tools menuitem in menubar relatively quickly after startup

Actual results:
Sometimes, Profils menu open instead of Tools menu, Because the Profilers menuitem are inserted at different times.
Screenshot https://youtu.be/zcPEboaBXds

Expected results:
Menu items should appear without time lag.

Keywords: ux-error-prevention
Whiteboard: [fidefe-profile-management]

Set release status flags based on info from the regressing bug 1931006

:jhirsch, since you are the author of the regressor, bug 1931006, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

status-firefox137: --- → affected
status-firefox138: --- → affected
status-firefox-esr128: --- → unaffected
Flags: needinfo?(jhirsch)
Severity: -- → S3
Flags: needinfo?(jhirsch)
Priority: -- → P3

Set release status flags based on info from the regressing bug 1931006

status-firefox140: --- → affected

Profiles is disabled by default so menu items appear after a short delay. Once we turn profiles on by default this should be fixed.

(In reply to Susmitha Burra from comment #3)

Profiles is disabled by default so menu items appear after a short delay. Once we turn profiles on by default this should be fixed.

Profiles is enabled by default in Nightly and development builds and we still see a delay so I think there is still something to be done here.

You need to log in before you can comment on or make changes to this bug.