Closed Bug 469378 Opened 16 years ago Closed 15 years ago

CTRL-Z (undo) reveals typed sentences in the search *after* clearing history

Categories

(Firefox :: Search, defect)

3.0 Branch
x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: jellegeerts, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4

For *whatever reason* passwords or any personal data could be entered in the search, it is revealable by using CTRL-Z (undo) after clearing the history.

Also, when private data is cleared, the contents of the search aren't cleared either.

(Yes it happens too when you check all the boxes in the "Clear Private Data..." screen.)

Reproducible: Always

Steps to Reproduce:
1. Enter something in the search (in the location bar).
2. Clear private data.

Actual Results:  
The history of entered sentences is still retrievable by using the undo functionality.

Expected Results:  
The history of entered sentences should also be cleared when clearing private data.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20081211 Minefield/3.2a1pre

Undo is grayed out after your steps to reproduce. Also Ctrl+Z does nothing.
Component: Security → Search
QA Contact: firefox → search
Version: unspecified → 3.0 Branch
You're right, I must have accidentally used CTRL+DEL instead of CTRL+SHIFT+DEL hotkey to try to clear the private data.

Also I noticed that CTRL+Z never works at all, is that intentional?
(In reply to comment #2)
> Also I noticed that CTRL+Z never works at all, is that intentional?

That is probably bug 418874, which now also affects the location bar.
WFM on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a1pre) Gecko/20090828 Minefield/3.7a1pre
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Seems to WFM as well now.
marking as verified (based on comment #5)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.