IE & version Targeting

[fasterthanlight™]

http://alistapart.com/articles/theyshootbrowsers



Discuss!!


I think Microsoft should just build a PROPER browser, and make it a required upgrade for the entire windows-universe. Why do they insist on being different from everybody? Why do they insist on adding all these one-off "features *cough*hacks*cough

Microsoft, in my opinion is in the middle of a slow and painful death

[Theros]

http://alistapart.com/articles/theyshootbrowsers



Discuss!!


I think Microsoft should just build a PROPER browser, and make it a required upgrade for the entire windows-universe. Why do they insist on being different from everybody? Why do they insist on adding all these one-off "features *cough*hacks*cough

Microsoft, in my opinion is in the middle of a slow and painful death


I totally agree with you that I/we shouldn't have to specifically code for a certain browser that by choice refuses to implement many of the standard valid web code that many other browsers support! I mean, wtf...I can't understand (even with their fear of losing control of the web, which they slowly are anyway) why they would purposely keep IE6 (and to a degree IE7 as well) so horrible in terms of web parsing...

However, I don't agree with you that Microsoft as a whole is in the middle of a slow and painful death (you might be just referring to the web stuff...if that's the case ignore this heh). I think a lot of people always think this...and well that's just not true period.

So anyway, note to Microsoft: Improve your browser game. It just might make some people like you better.

[fasterthanlight™]

Yea you may be right about microsoft,

It just ... really... pisses me off, as a developer who's entire job is HTML/CSS, all of my day-to-day headaches are IE induced.
Do they actually read the feedback people write about IE? Do they? I dont think so...

its just like Microsoft to think of an idea like this that *could* be a good idea if every browser was on the same page. But at the same time, this is just them scrambling for ideas on how to regain control of their slipping browser market share.

"Oh crap, our browser sucks... how can we fix it as easily and quickly as possible without rewriting the whole thing from scratch .. which is what we should have done for ie7 in the first place... "

First it was the * html hack.. which does work.. but is still a hack, now version targeting??
Screw you IE......

[Templarian]

IE8 will solve a LOT of these headaches... just give them them. Although yes for the size of their company they should be able to stay with standards more.

Meh... its not like the standards are that great. Heck we have XHTML and HTML 4.0 and more than ever very heavy JS coded sites because of AJAX. I mean browsers have to deal with a lot of repetitiveness.

I just hope that after 4.0 HTML is no longer seen and XHTML takes over as the standard. Also innerHTML was a bad move on there part... its easy to use but breaks logics of the doms.

[fasterthanlight™]

I agree,

I'm just saying, they need to reinvent the wheel instead of flogging a dead cat over... and over... and over.....

[Digitalosophy]

This is gobsmackingly audacious. Imagine a new version of Word that behaves exactly like the old version of Word unless the document it is processing contains a hidden instruction to unlock any new features. That’s what Microsoft is demanding that web developers implement. Unless you explicitly say otherwise, IE8 (and IE9 and IE10, ad infinitum) will behave exactly like IE7.


LOL is all I have to say. So when IE 9 comes out you would have to go back to older sites you've created and edit them so they can act the way they should in IE9?

Are you ****ing kidding me?

[icio]

I still don't understand why they're not doing this by doctype. Are they covering their ***** in-case they get it wrong again?

Back on my doctype idea, they say that version targeting will mean that old documents will be displayed correcty forever. Hasn't it occured to them that old documents also use old (if any) doctypes? When "modern" browsers encounter these older pages they render them according to these old doctypes. And so it will be in the future... HTML 5 will replace HTML 4 and XHTML 1.1 will replace XHTML Strict 1.0 and as time continues newer doctypes will be replaced... but future "modern" browsers will still display current day pages correctly because they will adhere to the relevant doctype to tell them what to do.

It's so obvious and they're so plainly missing the point that it's infuriating!

[Theros]

IE8 will solve a LOT of these headaches... just give them them. Although yes for the size of their company they should be able to stay with standards more.

Meh... its not like the standards are that great. Heck we have XHTML and HTML 4.0 and more than ever very heavy JS coded sites because of AJAX. I mean browsers have to deal with a lot of repetitiveness.

I just hope that after 4.0 HTML is no longer seen and XHTML takes over as the standard. Also innerHTML was a bad move on there part... its easy to use but breaks logics of the doms.

Even I have to disagree with you on this. From what I've read recently about IE8...there's not too much standard raising there so far....

[fasterthanlight™]

LOL is all I have to say. So when IE 9 comes out you would have to go back to older sites you've created and edit them so they can act the way they should in IE9?

Are you ****ing kidding me?


You can do that if you want, but from what I gather, if you've got a site that is version targeted to work with ie8 for example, when ie9 rolls out, and you have your site targeted to ie8... ie9 will render it as ie8, so in a sense, it kind of makes sense for Microsoft to do this... but like I said, this feels like a quick fix to their years and years of borked IE mumbo jumbo