Open Bug 1385754 Opened 7 years ago Updated 2 years ago

It takes time to change the state of the menu Undo (Ctrl+Z) in Library

Categories

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

Product:
Firefox
Component:
Bookmarks & History
Version:
56 Branch
Platform:
Unspecified
Windows 10
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox54 --- unaffected
firefox55 --- unaffected
firefox56 --- fix-optional
firefox57 --- fix-optional

People

(Reporter: alice0775, Unassigned)

References

Details

(Keywords: regression, ux-userfeedback, Whiteboard: [iris])

Reproducible: always Steps To Reproduce: 1. Create many bookmarks in a folder. Optionally restart browser 2. Open Library 3. Delete the folder and Undo (Ctrl+Z) 4. Immediately, Open "Organize" menu --- Observe status of "Undo (Ctrl+Z)" menu Actual Results: "Undo (Ctrl+Z)" menu is still enabled. After a while and checking the menu again, the menu turned to gray color(i.e, it is disabled). Expected Results: Immediately, "Undo (Ctrl+Z)" menu should be grayed out(i.e, it should be disabled).
Surely anything that before was happening "immediately", in the async world cannot be immediate. This will be part of the other perf investigations.
Menu status should be changed immediately even if the async command is doing something.
not going to block the feature. We are working on perf, so the problem should be minor, regardless it's mostly a secondary UI glitch.
No longer blocks: PlacesAsyncTransact
Priority: -- → P3
Manual testcase(s) for this exist in our test repository. They have been automated in the Iris test suite and are currently disabled due to this bug.
Summary: It takes time to change the state of the menu Undo (Ctrl+Z) in Library → {Iris} It takes time to change the state of the menu Undo (Ctrl+Z) in Library
Summary: {Iris} It takes time to change the state of the menu Undo (Ctrl+Z) in Library → It takes time to change the state of the menu Undo (Ctrl+Z) in Library
Whiteboard: [iris]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.