[Webkit-unassigned] [Bug 23346] Restore form control values to a wrong form

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 12 06:45:48 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=23346





--- Comment #35 from TAMURA, Kent <tkent at chromium.org>  2010-04-12 06:45:46 PST ---
(In reply to comment #33)
> Why are we inventing this form hash technique? No other browser has it, that I
> know of. Can we figure out what the behavior of other browsers is, please? We
> will have to construct tests carefully to avoid being confused by the
> back/forward caching feature. We need to know the behavior when a back/forward
> cache is not involved.

I investigated Firefox.
Summary: Firefox has a similar issue.  But it rarely make a problem because
Firefox has page cache.

I couldn't find a way to avoid page cache of Firefox, so confirmed the issue
with another way.
1. Change a startup configuration to "When Firefox starts: Show my windows and
tabs from last time"
2. Open a local HTML file with two forms, and fill some values
3. Close Firefox
4. Edit the local HTML.  e.g. exchange the location of two forms
5. Start Firefox again

Then, we can see incorrectly filled forms.

I looked the source code of Firefox.  It identifies target controls by id
attribute or simple XPath expressions with name attribute value and ordinal
number.

(In reply to comment #34)
> Good point. May be we don't need the hash, if we don't refill values when user
> hits back button, and the page is reloaded from server instead from cache.

Chromium has no page cache at this moment.  I'm afraid removing this refill
feature makes users unhappy.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list