Document. Form. Item
Existing problems:
ExistingCodeThere are many statements such as document. formname. Item ("itemname"), which cannot be run in MF.
Solution:
Use document. formname. elements ["elementname"]
Collection Object Problems
Existing problems:
In the existing Code, many collection class objects are used (), which is acceptable to IE and cannot be used by MF.
Solution:
Use [] as the subscript operation. For example, change document. Forms ("formname") to document. Forms ["formname"].
For example, change document. getelementsbyname ("inputname") (1) to document. getelementsbyname ("inputname") [1]
Window. Event
Existing problems:
Window. event cannot be run on MF.
Solution:
Mf events can only be used in the event. This problem cannot be solved. This can be changed as follows:
Original code (can be run in IE ):
<Input type = "button" name = "somebutton" value = "Submit" onclick = "javascript: gotosubmit ()"/>
<Script language = "JavaScript">
Function gotosubmit (){
Alert (window. Event); // use window. Event
}
</SCRIPT>
New Code (run in IE and MF ):
<Input type = "button" name = "somebutton" value = "Submit" onclick = "javascript: gotosubmit (event)"/>
<Script language = "JavaScript">
Function gotosubmit (EVT ){
EVT = EVT? EVT: (window. event? Window. Event: NULL );
Alert (EVT); // use EVT
}
</SCRIPT>
In addition, if the first line of the new Code is not modified, it is the same as the old code (that is, the gotosubmit call does not provide a parameter), it can only be run in IE, but no error occurs. Therefore, the TPL part of this solution is still compatible with the old code.
Question about the ID of an HTML object as the object name
Existing problems:
In ie, the ID of the HTML object can be directly used as the variable name of the subordinate object of the document. It cannot be in MF.
Solution:
Use getelementbyid ("idname") instead of idname as the object variable.
How to get an object using the idname string
Existing problems:
In IE, Eval (idname) can be used to obtain the HTML object with ID as idname, which cannot be used in MF.
Solution:
Use getelementbyid (idname) instead of eval (idname ).
The variable name is the same as the ID of an HTML object.
Existing problems:
In MF, because the Object ID is not the name of the HTML object, you can use the same variable name as the HTML Object ID, which cannot be used in IE.
Solution:
When declaring variables, add VaR to avoid ambiguity, so that it can run normally in IE.
In addition, it is best not to take the same variable name as the HTML Object ID to reduce errors.
Event. X and event. Y
Existing problems:
In ie, the event object has the X and Y attributes, and MF does not.
Solution:
In MF, event. X is equivalent to event. pagex. But event. pagex IE does not.
Therefore, event. clientx is used instead of event. X. This variable is also available in IE.
Event. clientx is slightly different from event. pagex (when the page has a scroll bar), but most of the time it is equivalent.
If it is the same, it may be a little troublesome:
MX = event. X? Event. X: event. pagex;
Use MX instead of event. x
Others:
Event. layerx is available in both IE and MF. There is no difference in the specific significance of this function.
About Frame
Existing problems:
In ie, the frame can be obtained using window. testframe, but not in MF.
Solution:
The main difference between MF and IE in frame usage is:
If the following attributes are written in the frame tag:
<Frame src = "/xx.htm" id = "frameid" name = "framename"/>
Then Ie can access the window object corresponding to this frame through ID or name.
However, MF can only access the window object corresponding to this frame through name.
For example, if the above frame label is written in the HTM in the top window, you can access
IE: window. Top. frameid or window. Top. framename to access this window object
Mf: only window. Top. framename can access this window object.
In addition, both mfand iecan use javasdesktop.doc ument. getelementbyid ("frameid") to access the frame tag.
In addition, you can switch the frame content through the parameter top.doc ument. getelementbyid ("testframe"). src = 'xx.htm '.
You can also switch the frame content through window. Top. framename. Location = 'xx.htm '.
In MF, the defined attributes must be obtained by getattribute ().
Parent node Problems
If there is no parentelement parement. Children in MF, use parentnode. childnodes.
Childnodes has different meanings in IE and MF. MF uses Dom specifications, and blank text nodes are inserted in childnodes.
You can avoid this problem by using node. getelementsbytagname. When a node in HTML is missing, ie and MF have different interpretations of parentnode, for example
<Form>
<Table>
<Input/>
</Table>
</Form>
In MF, the value of input. parentnode is form, while that of input. parentnode in IE is empty.
The node in MF does not have the removenode method. You must use the following method: node. parentnode. removechild (node)
Const Problems
Existing problems:
You cannot use the const keyword in IE. For example, const constvar = 32; in IE, This Is A syntax error.
Solution:
Use VaR instead of Const.
Body object
The MF body exists before the body tag is fully read by the browser, While IE exists only after the body is fully read.
URL Encoding
In JS, if the URL is written, write directly & do not write & amp; for example, VAR url = 'xx. jsp? Objectname = XX & amp; objectevent = XXX ';
FRM. Action = URL, so it is very likely that the URL will not be properly displayed, so that the parameter is not correctly transmitted to the server.
Generally, the server reports that the error parameter is not found.
Of course, if it is an exception in TPL, because TPL complies with the XML specification and requires & writes as & amp;
Generally, MF cannot identify & amp;
Nodename and tagname
Existing problems:
In MF, all nodes have a nodename value, but textnode does not have a tagname value. In IE, nodename usage seems to be
There is a problem (the test is not performed, but my IE has been killed several times ).
Solution:
Use tagname, but check whether it is empty.
Element attributes
The input. Type attribute in IE is read-only, but can be modified in MF.
Document. getelementsbyname () and document. All [name] Problems
Existing problems:
In IE, neither getelementsbyname () nor document. All [name] can be used to obtain the DIV element (whether there are other elements that cannot be retrieved is unknown ).