Earlier quoted context omitted.
what's the benefit of excluding the http:? I'd never seen that prior to a few years ago when the jQuery links started doing it.
It's a protocol relative link. So if the page is served over http, it'll be an http link, and if the page is served over https, it'll be an https link. See http://en.wikipedia.org/wiki/Protocol_relative_URL#Protocol-...
IE6 is dead
51–60 of 185 posts
Re: IE6 is dead
#52Re: IE6 is dead
#53Reports of its death are, from my experience, greatly exaggerated. It's still fairly widely used in businesses; as they say "if it's not broke, don't fix it." (Despite the fact that it is broken on many sites.) For anyone that wants to use a modern CSS framework that supports IE5.5+, check out Min ( http://minfwk.com ). Disclaimer: I made it.
I know this is a bit pedantic but it's definitely not 'fairly widely' or 'quite a lot' or 'some', there's a tiny, tiny percentage of businesses using it. Our UK website, not aimed at tech savvy, had 0.13% IE6 over the last 2 months compared to 0.32% the year before and when I last looked a significant proportion of that is bots and scrapers pretending to be browsers anyway. Half our traffic comes during the business…
Re: IE6 is dead
#54As others have pointed out, IE6 isn't dead yet. Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. And I'm afraid a lot of us have been complicit in the unusually long life of this dreadful monster, as well as of its just-as-dreadful offspring, IE8. By "us" I mean everyone who has ever developed a website in the last fe…
> If we really want to kill IE[6-8], we need to do something more drastic, and do so with extreme prejudice. How about we all agree upon a certain date on which we intentionally break our websites and services for IE6 users? Maybe for a blog, but I'm not telling 10%+ of my customers to piss off. If the cost of supporting them outweighs the value of their business then I won't support them any more. But I would never…
And is 10%+ of the Windows install base really XP???
Re: IE6 is dead
#55Just checked the analytics on a non-IT website: IE represents 10.45% Out of that: IE6 .28% IE7 2.03% IE8 19.81% IE9 16.57% IE10 16.15% IE11 45.13%
On utilitydive.com (covering the utility/energy industry) it's 35% IE and of that 40% is IE8. IE6 and IE7 are much less, but they also don't really work with our latest redesign so it's a bit hard to tell.
Re: IE6 is dead
#56At my employer, they finally pushed a full blown enterprise wide upgrade to IE10 with IE11 just around the corner (August). Unfortunately in parallel, they could not get enough people to submit sites that needed compatibility mode, so to prevent massive help desk problems they decided to push USE COMPATIBILITY MODE FOR ALL SITES. This basically downgraded everyone to IE7 mode permanently. So much for progress...
My Employer does this also, all sites are our intranet switch IE into IE7 compatibility mode. Does matter if the need compatibility mode or not. We recently released a version of the web app I am building and I wish you couldve seen the horror on our faces when we saw the app in IE 7 mode.
You can override this by setting X-UA-Compatible to IE=edge as a HTTP header on your server. The equivalent meta tag is ignored in this situation.
Or you could ask IT to change group policy, but I have no idea where that setting might live.
Re: IE6 is dead
#57Re: IE6 is dead
#58Re: IE6 is dead
#59As others have pointed out, IE6 isn't dead yet. Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. And I'm afraid a lot of us have been complicit in the unusually long life of this dreadful monster, as well as of its just-as-dreadful offspring, IE8. By "us" I mean everyone who has ever developed a website in the last fe…
But it's not. By keeping your website useable in Lynx, you make it a great deal easier for handicapped people to use your site. And to search engines. And to whatever more use cases there are (low bandwidth,..).
These concerns are just not valid for IE6. At least I can't think of any.
Also, you can always redirect the IE6'es to the same version as for Lynx, so you're not really refusing service...shrug