Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 7584 BUG: Session restore does not remember values for all of the fields
Starred by 2 users Reported by phistuck@gmail.com, Feb 11 2009 Back to list
Status: Duplicate
Merged: issue 17220
Owner:
Closed: Nov 2009
Components:
NextAction: ----
OS: All
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.


Sign in to add a comment
Chrome Version       : 2.0.160.0

What steps will reproduce the problem?
1. Enable the option to restore the last session on startup (regularly, not only 
after a crash).
2. Go to a page that has some fields to be filled (Say, http://code.google.com/p/chromium/issues/entry for example).
3. Fill in the "Summary" field and the "Description" field.
3. Close Chrome.
4. Start Chrome.
5. Go to the tab with the said page.

What is the expected result?
All of the fields will have last session values.

What happens instead?
The textarea ("Description") has the last session value, the "Summary" does 
not.
 
Labels: Feature-Sessions
This was complained about in the field, too:
http://pthree.org/2009/10/12/7-reasons-why-i-have-not-switched-to-google-chrome-from-
firefox/
"If my browser crashes, and I was typing an email, when I pull the browser back up, 
[on Firefox,] not only are my tabs restored, but the data in the tabs as well, 
including each tab history, and the text in any form fields that I was editing 
(provided I’m keeping a history of everything, as is default on a new install).... 
[But with] Chrome, form fields and text boxes that were once populated are now 
blank."

Comment 3 by tony@chromium.org, Oct 18 2009
Status: Assigned
We do restore text in text inputs and textareas.  I'm not sure why it's not working 
for the description field of the issue tracker, but I can repro the bug by:
1) going to crbug.com/new
2) typing in the description field
3) closing the tab
4) restoring the tab (ctrl+shift+t)

Comment 4 by sky@chromium.org, Nov 4 2009
Mergedinto: 17220
Status: Duplicate
This is another manifestation of 17220.
Project Member Comment 5 by bugdroid1@chromium.org, Oct 12 2012
Labels: Restrict-AddIssueComment-Commit
Mergedinto: chromium:17220
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 6 by bugdroid1@chromium.org, Mar 11 2013
Labels: -Feature-Sessions Cr-UI-Browser-Sessions
Sign in to add a comment