Summary: | charset ignored in enctype attribute of form element | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Andre-John Mas <andrejohn.mas> | ||||
Component: | Forms | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Normal | CC: | ap, ayg | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Andre-John Mas
2008-10-06 20:46:39 PDT
What do other browsers do? Created attachment 24147 [details]
Test case
Having run the test case under Windows XP:
Firefox 3: Content-Type: application/x-www-form-urlencoded
IE 7: Content-Type: application/x-www-form-urlencoded
Opera 9.5: Content-Type: application/x-www-form-urlencoded; charset=utf-8
Safari 3: Content-Type: application/x-www-form-urlencoded
Maybe I am just misinterpreting the RFC. Can anyone tell me what should be done? Maybe someone with ties to the w3c?
I doubt there's a better answer than "we should do what both IE and Firefox do". Also, I do not see anything in <http://www.w3.org/TR/html401/interact/forms.html> that would imply sending charset like this. So, this just sounds like an Opera bug. FWIW, WebKit's behavior here is correct per HTML5: http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#attr-fs-enctype Only the three literal strings "application/x-www-form-urlencoded", "multipart/form-data", and "text/plain" are allowed. (Saw this while searching for another bug.) Resolving as INVALID per all the above. |