I've got FA working on multiple sites hosted locally and remotely, and all of them seem to have stopped displaying icons on my laptop - I've done the obvious, tested on other devices and other browsers and I've found the latest IE appears to be the cause.
The IE version that does not work:
IE Version 11.15.16299.0
Update Code 11.0.47
Chrome works
IE version 11.0.9600.18762 works
So my own sites appear broken; but this public site that contains FA (the first result I came across on google) also appears to be broken...
https://fontawesome.bootstrapcheatsheets.com/
FWIW, glyphicons are not affected by this issue!
AFWIW, The official FA website works fine on the latest IE!!
Not been able to find anything on google so just wondering if anyone else is having this same issue and knows a fix?
So far I've tried:
Resetting IE settings & Delete cache/temp files
Try other devices (also have the same issue, with the same IE)
Try different FA sources; two CDN's and a local install - none fix the issue.
Thanks for any help :)
Chris
Update on this – I’ve just run Windows Update again, installed another pending Windows update and its working again. So there was an update on Monday that broke everything, and another released at some point since Monday that fixes it.
Something else I noticed a few minutes ago (before the issue was fixed) – I logged into Office 365 webmail and all the icons there were missing too! It’s pretty impressive stuff from Microsoft!
I'm trying to understand these strange rendering error boxes that are too big to be ignored. This seems to happen on Chrome in Windows 7 (my testing isn't too elaborate) and nowhere else. When I attempt to inspect, they all disappear. This could be some kind of video card issue as I'm using some pretty advanced CSS3 transitions that could mess up memory. In any case, if someone could offer advice on what I could do to fix, I'm at a loss. The site is www.crane-usa.com
Having the same issue with our site using 21.0.1180.89 and 21.0.1180.79. Problem is in Windows 7, Mac OS X latest, Ubuntu and in Chrome frame running in IE9. IE9 with Chrome frame disabled works fine. The problems are intermittent and unrepeatable. Inspect element removes the problem as you say. I tried disabling GPU compositing via chrome://flags but that didn't fix the issue.
We and our users have only been seeing these issues since approx Aug 27, 2012, 3 days ago. I took a look in crbugs.com and found that this seems to have existed for a couple of weeks already. http://code.google.com/p/chromium/issues/detail?id=143647
Sorry our site is not public so I can't post our url but you're not alone.
When loading a website (censored), it hangs for a couple of seconds before loading the page (up to a minute on older ones of internet explorer)
In other browsers it works fine.
It's a basic wordpress website with a couple of javascript and stylesheets, nothing to fancy. Firebug doesn't show anything weird in the NET-panel, all files exist.
Also with some other sites using the same plugin (for the properties), the same problem exists. So it should be plugin related, but I can't find why.
Any suggestions?
I loaded up IE9 and it loads quick. However, if you turn on IE9 dev tools, go to network, switch to IE8 standards mode and start capturing, you will see a lot of 404s on images that do not occur when using IE9 standards. This may be the issue. Good luck. – Matt Feb 23 at 16:55
Just to get the question answered, thanks #Matt
I'll try to be short and clean. I did website for friend, although she says some people complain about pink quote field to cover the text area, I've tried this on different PCs, browsers but haven't seen this kind of issue. So I was thinking maybe that old IE or something?
Here's websites link: http://www.zlobekbambino.pl
Thanks in advance
I would try using a service such as Adobe's Browser Lab or Browser Shots to test the site in various browsers to see which is causing problems. You can then try to work out how to fix it.
Assuming you have a Windows PC, you can test with all versions of IE by installing IETester. It's a very usefull program that allows you to run all versions of IE in tabs in the same window.
Obviously though, it only works on a Windows PC, so if you're on a Mac you won't be able to use it. In that case, http://www.browsershots.org allows you to download screenshots from virtually any browser ever released. The downside of that is that you only get a static screenshot, so not much use for testing dynamic content, but still a useful tool.
Is anyone writing applications specifically to take advantage of google chrome?
Are there any enterprise users who are considering using it as the standard browser?
Yes, I have started to pay very good attention to Google Chrome for my applications. Recent analytics show that between 6%-15% of my users are accessing my applications (varies between 6 to 15 in different applications) on Chrome. And, this number looks on an upward trend.
Thus, I can't really ignore it for testing right now.
As far as taking it as a standard goes, thats a long way off. I still have to test for IE6! :( Though, we have been planning to start using features like Gears (inbuilt in Chrome - downloadable elsewhere) once Chrome crosses the 25% mark. Thats when I believe that we will be looking at Chrome to be our preferred browser. I hope that we have Chrome 1.0+ by then! ;)
I switched to Chrome and haven't looked back except for the occasional site which doesn't work properly, forcing me to load it in Firefox. All my existing web applications work fine on it, and I'm using it for primary testing on my current development project.
I'm not actually targeting chrome, but I have added chrome to my browsers to test sites on. I've found some odd quirks in this product where some plugins cause the browser to hang, or run really slow in some environments, but they are still in beta in active development. But I definately now make sure sites I work on render well in chrome, as well as firefox, latest versions of IE, safari, Konquerer and opera. I usually check out how it looks on lynx as well, that helps me catch "un-alternated text" in images. Yeah, I know that isn't a word, but some people will understand what I'm saying.
Because chrome uses the webkit to render HTML, you can be assured if it works in safari, it'll work under chrome, however it's rendering engine isn't up to scratch quite yet. I think writing applications that take advantage of it is similar to writing iPhone applications, remember chrome is expected to be adopted by android to make it similar to iPhone. That way it pretty much takes advantage of all those iPhone apps.
Would I install it as the browser of choice? not yet - but i'll certainly work on valid web pages that will render across all browsers.
One of our major customers has outlawed Chrome because it installs on the C drive without asking. They deploy a standard image with a small C drive and large D drive so they can easily re-clone the system part of the image on C without destroying the client's personal files on D. Most software allows you to choose the install directory. Anything that violates this is disallowed, and they're a big enough company to have some weight with most vendors.
We have enough headaches trying to support
Firefox
Two versions of IE which have their own iffy bugs
Safari
I'm not sure why we continue to support Safari. Most of our users (corporate) use IE6 or IE7. We try to make sure that things work in both of those.
Maybe not for programming purposes but Chrome w/ Google Reader makes for the most powerful RSS reader. Can handle up to 1500 feeds w/ performance still ok, managing subscriptions still functioning.
I'm using it on my work machine, but that's about it. It's been stable for me, and I like the barebones UI. I'll still switch to Firefox for the web developer extensions however.
I'm liking some of GoogleChrome- the Start page with your 9 most recent is the winner for me. The interface takes a little getting used to, but the speed is impressive, especially with Gmail.
However, it glitches with Java, which rules it out for serious work at the moment. I use FireFox mostly and have Chrome for the "other" websites at work.
I'm considering using GWT on an intranet project and considering suggesting to the users that use Chrome to take advantage of the enhanced Javascript performance. Any AJAX-heavy app would be a great candidate to target Chrome.
At my company, we're not targeting it, but we're definitely paying attention to it. My boss is using it as his primary browser, and I have implemented browser detection for it in our scripts in case we ever to need to target it for some reason.
Chrome has the .png opacity bug where the transparent parts of the .png are a solid color if you try to transition the opacity from 0 to 1. In IE7 the opaque parts are black, and in Chrome, they are white. Today, I decided to go ahead and account for this bug in my JavaScript. I don't really test sites on Chrome that often, but I am actually using it for almost all of my browsing.
I will target Chrome as soon as a stable Linux and OSX client is available.
Targeting Chrome/Chromium right now, I think is like targeting Konqueror web browser. It will get popular, but you should wait to a more stable beta, and/or some Linux and OS X client.
My website statistics shows 3.xx % visitors using Chrome which arrived just few weeks back. And Opera is only 4.xx % which has been around for several years.
Easily you can see that rate at which Chrome is picking up.
You can see how easily Google takes over all areas of your computing world and personal world too.
Since Chrome uses Webkit, it has the same rendering engine and DOM support as Safari (not necessarily the same revision of Webkit though). By testing in Safari, you can generally get by without worrying about Chrome. Any differences you find are probably just bugs that you should file on instead of work around.
However, because Chrome uses a different JS engine, there may be a few incompatibilities with Safari. So, if you're doing anything with JS, you might as well fire up Chrome and see if there's anything obviously wrong.
Generally though, you don't target browsers, you target rendering engines (with their associated DOM support and JS engines).
I am using Google Chrome, so far all the web apps I have work fine in it with no modifications.
No.
Why help Google further build an evil empire? In this particular case it is so obvious that they do not care about users but only obsessed with gathering usage info.
It's not any major player yet