Summary: | REGRESSION(r106388): Form hidden element values being restored incorrectly for dynamically generated content | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Darth <priyajeet.hora> | ||||||||
Component: | Forms | Assignee: | Kent Tamura <tkent> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | ap, jonlee, morrita, priyajeet.hora, tkent, webkit.review.bot | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | All | ||||||||||
OS: | All | ||||||||||
Bug Depends on: | 89539 | ||||||||||
Bug Blocks: | 23346 | ||||||||||
Attachments: |
|
Description
Darth
2012-06-08 13:40:34 PDT
Created attachment 146643 [details]
form submit action file
https://bugs.webkit.org/show_bug.cgi?id=77391#c13 > I think the second one (saving hidden values updated after HTMLInputElement::finishParsingChildren()) is the safest for Bug 88685. Created attachment 148728 [details]
Patch
Comment on attachment 148728 [details]
Patch
Why is this only for hidden?
(In reply to comment #4) > Why is this only for hidden? We can detect whether the value is updated or not for other types because the current value is separately stored in other types. However the hidden type doesn't have such separated value. http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#dom-input-value-value Many types behave as "value" mode, and the hidden type behaves as "default". Comment on attachment 148728 [details] Patch Clearing flags on attachment: 148728 Committed r121519: <http://trac.webkit.org/changeset/121519> All reviewed patches have been landed. Closing bug. |