What could be the reviews related to targeting IE7 and using a tag that forces IE8 in IE7 mode in a new web application?

Question

I really don’t want to do this, I want to target the latest browser. It seems a little backwards to aim the old browser and then get IE8 to work in compatibility mode. I wonder what will happen when IE9 comes out?

However, jQuery and CSS have some problems that work correctly in IE8, it works fine in IE7 and Firefox, and I even consider Chrome. I want this thing to work well in IE7, IE8 and FF. Is there a better way or should I use this tag for IE8?

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

What are the risks for this? I just do not feel well, but I have no reason to support my fears. I get the feeling that this will cause problems in the future and create the potential for multiple processing, Thoughts?

UPDATE : here is the problem itself ...

if (dir == "back" || dir == "jump") {
     $.get(prevNode.attr("href") + "&bID=" + bID + "&ieRefresh=" + Math.random(), "",
          function(data) {
          p.nav.prevHtml = data;
     });
}

Error:

The object does not support this property or method string 390, character 37 (the character found by these "coordinates" is the dollar sign $ .get ()).

Answer 1

• Look at your code.
• See where you are doing it wrong.
• Correct your code.
• See how it works in IE8

, , IE8. IE7 FF Chrome .

IE8 IE9, IE9 IE6/7.

jQuery IE8. fanthom, CSS IE7 FF ( FF3.6 ? FF 1.5?), IE8. , - .

Answer 2

, jQuery IE8. CSS 7 8, jQuery, 8?

, IE ? .

<!--[if IE 8]>
Special instructions for IE 8 here
<![endif]-->

UPDATE:

$ , . "jQuery" "$" -? IE8 ....

Answer 3

IE8 IE9 IE7 ( - ), IE , , , , - .

, IE8 IE9. IE8 , , jQuery CSS 2.1 . IE , (, , ).