251 When we move past IE8? - A question about the futu

From what I’ve read (and this isn’t a great deal) this sounds like a good idea and even if only adopted by IE it’ll at least alleviate some headaches.

But I do have a question about how, as time moves on, older versions of browsers implementing this strategy will handle content targeted at later versions i.e. what will IE-8’s approach be when it encounters content targeted at IE-10:

I’d assume that in this situation it’ll adopt an ‘I’ll try my best to render’ rather than a ‘this page cannot be displayed as I’m not included’ approach.

I’d be interested to know what is intended as without this I think there may be issues when accounting for the fact that not all end users adopt new browser updates / versions either quickly or consistently.

posted at 03:03 pm on October 3, 2008 by Liam Prescott

252 Browser targeting

I definitely agree with Aaron, targeting a browser version using a meta tag is a great solution to a great problem, it’s simple, practical and at the same time elegant. I think browser targeting will leave its mark in Internet history, from this moment on it will be easy to completely understand (content + visualization + behavior) targeted web pages. Previous web pages will always require some archeological effort in order to be understood. My company, Artinsoft (www.artinsoft.com), has been developing tools to increase web sites’ code general quality and standards compliance (www.aggiorno.com). One of our tools, the IE8 Compatibility Wizard, automates the compatibility meta tag insertion task. I am confident that this tool can help several members of your audience and I sympathetically invite you to visit our web site and try our products.
I look forward to hearing from you.
Best regards,
César Muñoz
www.aggiorno.com
www.artinsoft.com

posted at 08:59 pm on January 9, 2009 by Cesar Munoz

253 code is code is code

Personally, I have to rewrite my sites at least every 3 to 4 years, often parts of some sites and some pages weekly (I want this new logo, I don’t like that color any more:-) ) As long as it is paid for I have no complaint.
SO, I don’t understand the argument about future/backward compatible pages. I want customers to update their material, and since I use includes I just change one file; update – reload and the site is all done! and I can go back to shoveling snow.
I would like for browsers to be standards compliant, I though that was the whole point of having standards in the first place. I think you guys (those who see this as a way out) have just been beat down by the Standards Compliant” struggle and the “meta-code” snippet is an easy way out. The last time I looked (last week?) the IEs were down at 37% and dropping and FF was at at 45% and rising. I look forward to Standards Compliance growing and the continued growth of standards compliant browsers.

v

posted at 09:37 am on February 19, 2009 by Vilppu Tilli

254 What about Javascript

This is indeed a nice approach if your application is huge and you want to make it compatible with new version of IE i.e. IE8.
I am using this with my web application, but I am facing some problem. When I try to open a lightbox that time the window of lightbox is not getting compatible with IE8.I guess the issue is with javascript.So I am not getting how should I make my layout(which is build with javascript at runtime) compatible with IE8. what could be the solution??

posted at 08:05 am on August 5, 2009 by shruti_hj

255 Detrimental to Web Standards

I agree this solution (implementation aside) may help solve catastrophe when a new browser is released. However we only need to look at the outcome of other applications where we force specifics in a browser to see where this path will take us. These days I’m pretty sure I only see IE6 running within companies that spent a small fortune on custom software that requires they stay in the IE6 box to function.

Do we really want to encourage the same type of behavior within basic web development? I work with enough “old school” clients to know that the vast majority would prefer to upgrade their old outdated site in the “HTTP-EQUIV” it was originally written in than redo everything with a new more modern solution. The last thing we want to do is promote locking our clients to a specific(and dated) browser, even if it does prevent a small period of panic.

posted at 10:07 am on August 30, 2011 by BryanSalva