ps4 ff

P {+ color: # f00;} supports IE6 IE7 and does not support FF IE8P {_ color: # f00;} supports IE6 and does not support FF.P {color: # 00f! Important ;}P {color: # f00;} supports IE7 IE6 FF IE8P {color: # 00f! Important; color: # f00;} supports IE7 IE8 FF and does not support IE6Head: first-child + body p {color: # f00;} supports IE7 IE8

FF Firebug, not only can test JS can also check CSS errors, is generally used.But it is mainly to check the FF error, IE is powerless.To test IE, use ietester, it can test almost all versions of IE (1.0 I'm afraid it won't be tested), usage is also very convenient.As for JS to different browser compatibility considerations, indeed a lot, the following is only part of you, general advice or use jquery,protot

css| Solve | The problem Previously found several different versions of the Internet Explorer can run independently, just to try to test the compatibility of the page. Don't try not to know, in IE6 and FF no problem page in IE5 and IE5.5 mess, has been heard that IE5 is a Web standard production of a "nail", now have to believe. Since there are problems, then find a solution to it, a search on the Internet, the relevant articles or a lot of, think the

(Experience) Div + CSS solves IE6, IE7, IE8, and FF compatibility problemsLet me talk about it. After nearly a year of Div + CSS, we have accumulated many methods to solve compatibility problems. Here I only talk about the mainstream ones (IE6, IE7, IE8, ff) others have not been studied.1. For compatibility issues in IE8, it is best to solve this problem by converting it to IE7 compatibility.Add the followi

Turn from Blue Ideal Author bias Original Address http://www.blueidea.com/tech/site/2006/3296.asp Previously found several different versions of the Internet Explorer can run independently, just to try to test the compatibility of the page. Don't try not to know, in IE6 and FF no problem page in IE5 and IE5.5 mess, has been heard that IE5 is a Web standard production of a "nail", now have to believe. Since there are problems, then find a solution to

Differences between JS and CSS in IE and Firefox (FF) CSS: 1. In the UL tag, FF has a padding value, but there is no margin value. In ie, the opposite is true. Solution: Set UL's padding and margin to 0 (or not 0), for example, padding: 0; margin: 0; List-style: none; JS: 1. In IE, innertext is not in ff, and textcontent is used; Eg: CopyCode The Code is

Differences between js and css in IE and FireFox (FF)Css: 1.In the ul tag, FF has a padding value, but there is no margin value. In IE, the opposite is true.Solution: Set ul's padding and margin to 0 (or not 0), for example, padding: 0; margin: 0; list-style: none;Js: 1.In IE, innerText is not in FF, and textContent is used;Eg:Copy codeThe Code is as follows:Var

1. If an html Tag is set to $ (id) or getElementById, you must add the id attribute to the tag. IE and FF are compatible. For example, $ (mobile): If the input of mobile does not have the id attribute, the variable undefined will be reported in FF;2. Take a tag object in the form. If you want IE and FF compatibility, change formMain. item to document. formName. i

1. Custom attribute problems: You can get custom properties by using methods that get general properties, or you can use Getatribute () to derive a custom attribute, and only use getattribute () to derive a custom attribute under FF.2. In IE, you can use eval ("Idname") or getElementById ("Idname") to obtain an HTML object with ID idname, which can only be used with the latter, the solution, and unified getElementById acquisition.The ID of the HTML ob

corresponding to the function in FFLike what:function (e) { getObject (this, e| | event); // box captures the event and processes e-->ff window.event-->ie };Of course there are times when you can think of this: Use Global object Arguments[0] to replace captured event arguments// dis = arguments[0]| | window.event; If the above sentence cannot get the event under FF, I hear that the

I. Problems: Var xmlHttp;Function savecarttodata (){ CreateXMLHttpRequest ();Var rndcode = new Date (). getTime ();Var CartUrl = "a. asp? Cache = "+ rndcodeXmlHttp. onreadystatechange = function (){..... }XmlHttp. open ("GET", CartUrl,True);XmlHttp. send (null );} The code above, xmlHttp. onreadystatechange = function () {...}; can be executed in FF, but if it is changed XmlHttp. open ("GET", Url,False); It will not work at the moment. Today, I am con