New Versions of Chrome Were Bugging Out [FIXED]
Page 1 of 1
#1
21 June 2013 - 07:13 PM
A few of you have reported running into <a href='http://productforums.google.com/forum/#!topic/chrome/zID6uQQfKH8' class='bbc_url' title='External link' rel='nofollow external'>this bug</a> when browsing the site with Chrome and reloading pages. While Chrome fixes the CSS reloading error with an update, you can work around the issue by using Shift + F5 instead of reloading normally. This will force Chrome to reload site assets and bypass the bug.
Click here to view the article
Click here to view the article
#2
21 June 2013 - 08:49 PM
Yes I've run into this problem frequently the past few days. Thanks for the fix Archael.
#5
31 July 2013 - 07:31 AM
Why don't they see it as a legit bug? Is it something with YOUR coding that triggers the bug? Otherwise I don't get it.
#6
31 July 2013 - 11:13 AM
No problems for me. Plus, I'm even using actual Chrome now and not a knock off. No more Flame Fox for me. lulz
#7
31 July 2013 - 03:37 PM
I realized that [Shift]+[CMD]+[R] worked just as well (actually, even better), and is easier despite being one extra button. I'm assuming that the Windows equivalent would be [Shift]+[CTRL]+[R], but haven't tried it out.
#10
02 October 2013 - 03:47 PM
Update on this: The new versions of Chrome have fixed this issue. Just update your browser.
#13
02 October 2013 - 06:54 PM
I started using Firefox because of ID chat and bug. So, I can finally reunited back with my old Chrome.
Share this topic:
Page 1 of 1