Tag Info

Hot answers tagged

2

Ok, so we have confirmed that our calculations were incorrect. Our provider was giving us reports based on the number of "visits". A visit is calculated based on the amount of time a user spends on our website. However, IE7 users might be rare but they might spend more time on a website compared to a Chrome user. This meant that the percentage we were going ...


2

Check out this question on Stack Overflow, http://stackoverflow.com/questions/4031718/favicon-is-pixelated-in-ie. It looks like 32x32 pixel favicons look much better in IE7 than 16x16. The only down side is Chrome only supports 16x16. Here is an article going in depth into how favicons work and what your options are, ...


2

IE7 is obviously going to become the new IE6; however, it's not entirely out the door yet. Whether it makes sense for you to support it, will entirely depend on your user base and other factors. The answers given on this webmasters. Stack Exchange question: should I bother supporting IE6? essentially basically apply to any version. I'm in charge of a ...


1

It turns out that the solution, at least in my case, is to save in 32x32 .ico format but with the transparency turned off. In addition - when I use this in MediaWiki it only goes wrong using the default name: favicon.ico. When I use a non default name, the problem goes away! In Local Settings.php: $wgFavicon = '<name>.ico';


1

Nice of you to ask this. I generally do not bother optimizing for a browser whose share on my site is not more than 5% (yes, even I got IE7 in that segment). You could also have a small IE7 specific notification in the footer which says that the site experience is optimized for IE8 and above?


1

Your friend in this kind of situation is cURL. A really really quick tutorial... Use curl's view headers only option (-I) to see what headers the server returns on your published domain: curl -I http://www.nulc2012.com/ I got this response, which says that a Permanent Redirect 301 is being sent to the browser, along with the target URL: HTTP/1.1 301 ...


1

Force Chrome Frame for IE with conditional statements. When the web breaks for enough for IE 7 users then they will upgrade and not until then. Remember the Ai, the three-toed Sloth of the Bradypus family, that is your IE7 user. Our Google Analytics showed 7% IE7 usage until Chrome Frame, now its 2%. There's no telling some people. Also, segment your data by ...


1

It depends who will be using your product. Even if IE6 is ages old and the alpha geeks say it's dead, there are still people who are using it. Same with IE7, except that it's probably used by more people than IE6. So, if your product is only for alpha geeks, drop IE7 support. If everyone should be able to use it, you probably should support IE7 (and dare I ...



Only top voted, non community-wiki answers of a minimum length are eligible