Open
Bug 722640
Opened 14 years ago
Updated 9 months ago
"Undo Add to Dictionary" is not very useful after time passes since dictionary addition
Categories
(Core :: Spelling checker, enhancement)
Tracking
()
NEW
People
(Reporter: MattN, Unassigned)
References
Details
(Whiteboard: dom-lws-bugdash-triage)
(Alex Limi (:limi) — Firefox UX Team from bug 352037 comment #17)
> A simple way would be to include an extra item in the context menu “Undo
> adding ‘XYZ’ to the dictionary” and make it only appear when there's
> something that was just added — ie. the “oops” case.
There are two details which don't align with Limi's suggestion:
1) The initial implementation in bug 352037 adds a context menu for the rest of the browser session once a word is added to the dictionary. This is too long of a time period to solve the "oops" case. It adds extra distraction with a very small likelihood of use after a few seconds because...
2) The menu item doesn't display the word that will be removed from the dictionary. After some time passes, it's very unlikely the user will remember if a word was accidentally added.
Some possible solutions:
1) Save the undo state with each page/field instead of globally. When the page changes, the undo history is cleared.
2) Clear the undo state after a delay.
3) Show the word to undo in the menu so at least the user will be reminded of the word in question.
Comment 1•14 years ago
|
||
Yeah, I was under the impression that at least this was already in the patch:
3) Show the word to undo in the menu so at least the user will be reminded of the word in question.
That should take care of most cases — if it's trivial to do it on a per-page basis, we should do that, but showing which word will be removed from the dictionary is at least a great improvement.
Keywords: uiwanted
Comment 2•12 years ago
|
||
I like some of these options. #3 sounds like the most critical. Has anything been done in the last year and a half? From the age of the existing comments, this bug has just sat there. :(
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•