Updates:
Status: Fixed
Comment #4 on issue 4296 by bre...@chromium.org: Form state is not saved
when it should be
http://code.google.com/p/chromium/issues/detail?id=4296
Fixed in r7549.
--
You received this message because you are listed in the owner
or CC fields of this issue, or bec
Comment #3 on issue 4296 by [EMAIL PROTECTED]: Form state is not saved
when it should be
http://code.google.com/p/chromium/issues/detail?id=4296
I checked in a change in WebKit in r39152 that adds the ability for us to
implement
this properly.
--
You received this message because you are l
Issue 4296: Form state is not saved when it should be
http://code.google.com/p/chromium/issues/detail?id=4296
Comment #2 by [EMAIL PROTECTED]:
I filed https://bugs.webkit.org/show_bug.cgi?id=22177 for the WebKit side
of this.
Issue attribute updates:
Status: Assigned
--
You received
Issue 4296: Form state is not saved when it should be
http://code.google.com/p/chromium/issues/detail?id=4296
Comment #1 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Pri-2 Pri-1
--
You received this message because you are listed in
Issue 4296: Form state is not saved when it should be
http://code.google.com/p/chromium/issues/detail?id=4296
New issue report by [EMAIL PROTECTED]:
When the user changes a form value, we should periodically sync that form
state to the browser for session restore and crashed tab recovery. This is
