Closed
Bug 73943
Opened 24 years ago
Closed 24 years ago
form.encoding property not working properly...
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
mozilla0.9.1
People
(Reporter: fred.lorrain, Assigned: jst)
References
Details
(Whiteboard: [XPCDOM])
Attachments
(1 file)
715 bytes,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
BuildID: 2001032319
This property is a read-only property.
There is absolutely no reason to do that.
In IE I can set this property with a javascript.
With mozilla it's imposible because this property is read-only.
Reproducible: Always
Steps to Reproduce:
1. Create a form called TheForm.
2. Try to set the value of the property encoding of the form object.
Example :
document.TheForm.encoding = "multipart/form-data";
Will return an error
Actual Results: The script stops because of the error.
Expected Results: Set the property encoding as read/write.
This bug exists of course also in Netscape 6 and 6.01
Comment 1•24 years ago
|
||
browser, not engine. Over to DOM HTML.
DOM2 says that the property is called enctype, not encoding, by the way...
This is certainly not a blocker
Assignee: rogerl → jst
Severity: blocker → normal
Component: Javascript Engine → DOM HTML
QA Contact: pschwartau → desale
Assignee | ||
Comment 2•24 years ago
|
||
form.enctype is the standard way of doing this, form.encoding is an IE:ism only
that is not supported by mozilla. I'll fix this with my XPCDOM changes...
Could someone attach a trivial testcase?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: encoding form property → form.encoding property not working properly...
Whiteboard: [XPCDOM]
Target Milestone: --- → mozilla0.9.1
Comment 3•24 years ago
|
||
Comment 4•24 years ago
|
||
Mozilla appears to support encoding as a readonly alias for enctype (apparently
this was originally how IE treated it).
The attached testcase shows that Mozilla currently reflects changes to enctype
in encoding but not vice versa.
Reporter | ||
Comment 5•24 years ago
|
||
If you define enctype under IE, the encoding property will not be updated.
If you define encoding under IE, the enctype property will not be updated.
IE use only the encoding property. There is no error if I set the value of
enctype under IE but IE will not use it.
So to be Mozilla and IE compatible I have to set encoding if the browser is IE
and enctype in any other case.
Assignee | ||
Comment 6•24 years ago
|
||
You will soon be able to set .encoding and it'll work in both browsers. IE is
the one that's broken here tho, I'm making .encoding work in mozilla to be
compatible with IE's broken behavior only.
Assignee | ||
Comment 8•24 years ago
|
||
Fixed by the xpcdom landing.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 10•24 years ago
|
||
verified on linux and windows...
Build ID:
windows - 2001-06-07-06-0.9.1
Linux - 2001-06-07-13-0.9.1
Status: RESOLVED → VERIFIED
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in
before you can comment on or make changes to this bug.
Description
•