29 Dec 2013 1:10 AM #151
29 Dec 2013 5:17 AM #152
You'll have to forgive my scepticism but I've never observed this behaviour in any browser and it seems unlikely that something so fundamentally broken could make it into a released browser. Even if it did I can't see how a library as complex as ExtJS could possibly work with such a buggy JS engine, it'd collapse in a heap long before reaching that code.
Even more unlikely is that such a serious bug observed in October 2012 (according to that SO question) would still be present now.
If you can provide specifics (affected browser version, confirmed browser bug ticket, etc.) I'd be more than happy to change my mind.
In my opinion a much more likely, albeit uncharitable, explanation is that you're simply misinterpreting what you're seeing.
4 Jan 2014 12:42 AM #153
Seems like your skepticism is pertinent. I tried to reproduce and had no luck