Ie and firefox distinction among the Js and Css

1 object problem
1.1 Form object
existing problems:
existing code which access the form object by document.forms (
solution:
use for subscripting. To document.fashions [in IE, HTML document object ID can be a subordinate object as a variable name instantly. In the MF can not.
document.all (
Remarks
document.all is IE-defined methods, so please try not to use.
there a way in IE and MF can be used
var f = document.forms [> present issue:
in IE, DIV object ID can be used directly as an object variable name. In the MF can not.
DivId.manner.display = DIV object method or not, use the getElementById method. See 1.2

1.4
on frame
existing problems in IE can window.testFrame obtain the frame,Women FiveFingers Performa Jane, mf not
solution
in the frame of the MF and the use of The main feud is that IE:
if written in the frame label in the following attributes:
then IE can access the id or name corresponding to the frame window object
and mf can only be accessed at this name frame corresponding to the window object
example, if the frame label written aboard the top of the window inside the htm which then can be accessed
IE: window.top.frameId or window.top.frameName to access the window object
MF: window.top.frameName only way to access the window object
In addition, the mf and ie can be accustomed window.top.document.getElementById (and can be window.top.document.getElementById (alternate frame content
1.5
existing problems
IE window can be opened by showModalDialog and showModelessDialog modal and non-modal window, but the MF does not support.
solution
straight use window.open (pageURL, name, parameters) way to open a new window.
If you need to pass parameters, you can use frame or iframe.
2.
2.1 summarizes the manifold objects defined in the JS variable name, try to use the id, to avoid name.
in IE,Vibram FiveFingers New Styles, HTML document object ID can be a subordinate object as a variable name directly. In the MF can not, so please try to use normal use id, avoid using only name, instead of using the id.
2.2 variable name with an HTML object id the same problem

existing problems in the MF, because the object id is not the name of the object as HTML, so you can use the HTML object id with the same variable name, IE can not.
solution
in a statement variables, all with var, to avoid ambiguity, this can also be run in IE.
In addition, it is best not to take the HTML object id with the same variable name in mandate to dwindle errors.

1. document.all
Firefox compatible document.all, yet generates a advising. You can use the getElementById (
2. parentElement
this is not compatible. For sample, obj.parentElement.name ought be changed to obj.parentNode.attributes.getNamedItem (W3C does not support windows.accident
example:
in IE

function onMenuClick (evt)

if (evt == null)
evt = window.event; / / For IE
var srcElement = evt.srcElement? evt.srcElement: evt.target; / / IE use srcElement, while Firefox uses the target
collapseMenu (srcElement);


IE and FIREFOX CSS parsing the difference between districts of high resolution

IE: height of the content will change, including the highly defined image content, even now the definition of the height, When the content exceeds the height, it will use the substantial height
Firefox: height is not defined, if the content includes image content, MF is based on high resolution printing criteria, this will occasion a high degree and the actual content does not meet the position; When defining the height, but more than the content height, the content is outdoor the defined height, but does not change the style used in the region, resulting in dislocation style.
Conclusion: We tin resolve the content altitude in the case of the best meaning of height, whether truly not way apt define the height, no the best use of siteline styles, alternatively styles namely there ambition be confusion!
img alt and title of the resolution object
alt: When the photo does not exist or load error hints;
title: photo tip description.
in IE if no title, alt tip can also be used as img, but in the MF, the 2 are completely in agreement with the standard definition used
Conclusion: We define img object, and eventually the alt and object to write the entire heading, ensure that all browsers can be used normally
other details of the differences
When you write css period,Women Vibram FiveFingers Speed, primarily with the float: left (or right) laid in a channeling picture , you will find inside normal in firefox and IE there are problems. Whether you use margin: 0, or border: 0 to repress, to no advantage.
truth, there is different issue here, is a space for the treatment of IE, firefox and IE is ignored for blocks and blocks the spaces between the deal. That is followed by a div after the end of a div to write in the middle do not have chariot returns or spaces. Otherwise, there may be problems,Vibram Five Fingers, such as 3px discrepancy, and for this reason laborious to find.
quite lucky that I ran into this problem, a number of img tag accompanied, and then define the float: left, wish these pictures can be put together. However, regular results in firefox and IE inside each of which displays are separated by a img 3px. I have cleared the spaces among the labels have no achieve.
afterward solution is set out in the img li, and the definition of li margin: 0,Vibram FiveFingers Sprint, this would determine the IE and firefox display prejudice. IE fall butme models to explain the publish will have a lot of faults, fair try to ascertain a lot of causes.
This is just some easy difference, act the layout and CSS design time can be taken into account, but the most forcible and simple solution to compatibility problems, or with TABLE chart, the table has a nice compatibility in the extravaganza.
Also in JS template design, they likewise absence to think both the code compatible with IE and FIREFOX following are some tests in JS:
the following to IE instead of Internet Explorer, to MF instead of Mozilla Firefox
1. document. form.item problem
(1) existing problems:
existing code, there are numerous document.formName.item (can not sprint in the MF

(2) Solution:
use file.formName. units [
many of the existing code to use a accumulation class object access (), IE can adopt, MF can not.
(2) Solution:
use [] as subscripting. Such as: document.forms (
Another example: document.getElementsByName ((MF window.event can not run on
(2) Solution:
MF of the event can only use the scene of the episode, can not solve this problem temporarily. Can be modified:
the aboriginal code (can be run in IE):

current code (which can run in IE and MF):

In addition, if the new code does not change the premier line, the same object with the old code (that is, not to cry gotoSubmit
parameters), is still only running in IE, but not go wrong. Therefore, this portion of the program is still with the old
tpl code compatible.
/////////////////////////////////// ////////////////////////////////////
; / / The following comes from consumers llihua
/ / event handler
function a (evt) / / FireFox
evt = evt? evt: window.event; / / IE
var srcElem = (evt.target)? evt.target: evt.srcElement;
/ / event handling ...

in linkage event handler when you can use the Inline HTML method, you can with Event
property defined.

1, using Inline HTML usages, such as:

ie can you access the id or name corresponding to the window frame and mf only object
by name to access the frame corresponding to the window object
example, if the frame label written on the top of the window inside the htm which then can be accessed
; ie: window.top.frameId or window.top.frameName to access the window object
mf: only this window . top.frameName to access the window object
In addition, the mf and ie can be used in
; window.top.document.getElementById (
and can
window.top.document.getElementById (. src = 'xx.htm'
to switch the contents of the frame can also be passed window.top
. frameName.place = 'xx.htm' to switch on the frame of the frame and window content
portrayal can be found in bbs's 'window and frame' article
; and / test / js / test_frame / catalogue test
---- adun 2004.12.09 adjust
9. mf in their defined properties must getAttribute () to obtain
10. parentElement parement.babies not in mf and use
parentNode parentNode.childNodes
childNodes meaning of the subject below different in IE and MF, MF to use the DOM description, childNodes inserted into the vacant
text nodes.
generally can node.getElementsByTagName () to avoid this problem.
When lacking html node, IE and MF for different interpretations of parentNode, such





MF in input.parentNode amount form, meantime in IE input.parentNode is empty in the node
MF node does not removeNode method, you must use the following method
node.parentNode.removeChild (node)
11.const problem
(1) existing problems:
in IE not using the const keyword. Such as const constVar = 32;
in IE, this is a grammar error.
(2) Solution:
do not use const, with the var instead.
12. body object
MF's body in the body tag has not been completely read into the explorer before the subsistence of the IE have to be entirely read into the body afterward
there
13. url encoding
written in the js in the url if you do not directly write & write & such
var url = 'xx.jsp? objectName = xx & objectEvent = xxx' ;
frm.movement = url then promising will not be exhibited properly so that the url parameter is not correct to the waiter
server misdeed parameter is not normally base in the tpl
course, if the exception Because tpl in line with xml specifications, requirements & writing because the general MF &
not acknowledge js in &

14. nodeName and tagName issues
(1) existing question:
in MF, all nodes are nodeName value, but textNode not tagName value. In IE,
nodeName
use if there are problems (not tested the specific situation, but my IE has been dead several times).
(2) Solution:
use tagName, but should be found is empty.
15. element attributes
IE under input.type read-only property, but can be modified under ME

16. document.getElementsByName () and document.all [name] problem
(1) existing problems:
in IE, getElementsByName (), document.all [name] can not be used to get a div element
(Are there additional elements can not take not know).
17. DOM data island issues
(1)
existing problems in IE, tag has a special significance, can be included XML DOM, and HTML components and can accomplish file
fastening in the MF in, is just an nameless tag only.
In counting, the IE is,Vibram Fivefinger, really manner here is an ActiveX object, but it hung in the HTML DOM tree of the
body as a node , which traverses the DOM tree would be seriously affected.
(2) solution
IE data binding mechanism is to use JS to pretend, but too many distress, it is recommended not to use data binding machinery or
find the library to do to achieve this simulation, we only argue how to appliance the DOM compatible.
Known in the MF in both HTML tags or other marks in line with the XML specification, the DOM tree are used to handle with a unified
, therefore, MF in fact can use the DOM data isle, but with little difference between IE: In IE
is a DOM document, and in the MF only DOM node. This difference is routinely less infestation.
But there is a small elaborate, in order to fairly overbearing syntax compatible with HTML, MF does not recognize the contraction of the empty jot.
such as: and is shorthand, MF will not recognize, it should be written as:

However, I mistrust if XHTML, may not have this problem, but I have not tried.
For IE, the HTML DOM building interference problems, the way I deal with it after the
DOM from the HTML in the erased. do not know no better solution.