Jump to content
|Topic||Stats||Last action by|
|Play Store price monitor/tracker||
|Boy died and was revived 3 times after car accident||
|What is the single change that that has had the greatest effect on your life?||
|Google aims to paint a picture of a perfectly healthy human being||
|GM announces another 6 recalls covering nearly 718,000 US vehicles||
Posted 09 May 2013 - 01:42
Posted 09 May 2013 - 08:41
Its staggering how many sites' crap devs were exposed by IE10.
I'm having problems replying on Chrome OS. Just started today. It works fine with Chrome on Windows.
Posted 09 May 2013 - 12:32
If you're using a dev version, then I'm not surprised. I'm on Chrome beta which is generally problem free, but I don't have any experience at all with Chrome OS
Posted 09 May 2013 - 12:44
Posted 09 May 2013 - 15:42
IE10, best browser eva!
It's not as simple as that at all.. Sites generally have to account for backwards compatibility for many versions of a browser, if we coded Neowin (as we do) only HTML5 compliant, then quite a few browsers wouldn't work, so we're forced to do a mix of both modern and compatible.
Anyway, it's IPB at fault here, not us. The Neowin main site is fully compliant with IE10.
I'm on Chrome beta which is generally problem free,
Posted 11 May 2013 - 04:47
Posted 17 June 2013 - 16:30
Posted 18 June 2013 - 10:54
Test IE10 fast reply.
IE10 editing still not working after upgrade FYI. (Its actually worse now)
Posted 18 June 2013 - 11:04
Still some issues remain, but as I type this, I was presented with the rich text editor. Been a while since I've seen it in IE10.