Open Bug 340380 Opened 18 years ago Updated 2 years ago

Undo is per-textfield, instead of being global for the whole tab

Categories

(Core :: Layout: Form Controls, defect)

defect

Tracking

()

People

(Reporter: hwaara, Unassigned)

References

Details

(Whiteboard: Needs usability testing; I suspect wontfix)

Tested on Firefox 1.5.0.3 and Camino 1.0.1 on Mac OS X.

PROBLEM:  Doing "undo" seems to be tied to the currently focused textfield, rather than being a global application action.

TO REPRODUCE:

1. Go to any page with more than one textfield
2. Write something in textfield #1
3. Focus and write something in textfield #2
4. Undo a few times, until you can't anymore.

EXPECTED RESULT:

Doing undo should first undo the text in textfield #2 and finally also textfield #1.

ACTUAL RESULT:

You can only undo the text written in the currently-focused textfield. If you want the undo whatever you did in textfield #1, you need to first focus it.

Not sure if it's a core bug, or if a bug needs to be filed on every application.
Application-global seems a bit wide.  I don't want pressing Ctrl+Z too many times to undo my typing in a background tab and then undo adding a bookmark.
True; make that per-tab instead (or "page").
Summary: Undo is per-textfield, not an application-global action → Undo is per-textfield, instead of being global for the whole tab
I would find it utterly confusing if pressing cmd-Z in one text field would cause something to happen in another field.

In other words, I vote against "fixing" this "bug".
I find it confusing in a form that each single-line textfield would have its own "undo stack". I think of the form as one coherent thing that I'm editing, whether I just changed an option in a <select>, or wrote something in a textfield.
I agree with comment 3, but it's something we should test with usability testing, if we want to make an educated decision.
Whiteboard: Needs usability testing; I suspect wontfix
is this a duplicate of #92710 ?
sorry, direct link: bug 92710
Blocks: 468835
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.