[Webkit-unassigned] [Bug 8683] New: HTMLInputElement::state can't distinguish null string from empty string
bugzilla-daemon at opendarwin.org
bugzilla-daemon at opendarwin.org
Mon May 1 09:18:44 PDT 2006
http://bugzilla.opendarwin.org/show_bug.cgi?id=8683
Summary: HTMLInputElement::state can't distinguish null string
from empty string
Product: WebKit
Version: 420+ (nightly)
Platform: Macintosh
URL: http://imdb.com/title/tt0120907/
OS/Version: Mac OS X 10.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: Forms
AssignedTo: webkit-unassigned at opendarwin.org
ReportedBy: coldwinter at katamail.com
CC: darin at apple.com
This bug has previously been reported in the comments of bug 7691.
How to reproduce this:
1 - Go to http://imdb.com/title/tt0120907/
2 - Click on "David Cronenberg".
3 - Go back using Safari's back button.
4 - The search button is rendered incorrectly.
This happens in TOT (r14126).
Darin said about this:
The new bug doesn't have to do with the button rendering itself, but rather
with the way form data is saved and restored. Apparently a null is saved, but
an empty string is restored, or vice versa.
The fix will be to change HTMLInputElement::state and
HTMLInputElement::restoreState so they can distinguish a state of null string
from a state of empty string, which should be straightforward.
--
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list