3 ms·
I'm still very wary of this new browser. Microsoft keeps saying since IE9 that they finally delivered, but it's not the case yet. IE still lags behind and still
by pdknsk 12y ago
I'm still very wary of this new browser. Microsoft keeps saying since IE9 that they finally delivered, but it's not the case yet. IE still lags behind and still has quirks.
I actually downloaded the IE11 VM from http://modern.ie http://modern.ie the other day to give it another chance. A not very pleasant experience. After boot, I was greeted with a desktop background with some instructions, presented as a badly compressed JPEG. I'll be honest, and vote me down if you must, but I'd be ashamed to have delivered this kind of work. Make it a PNG or a BMP even, it's not going to inflate the 4GB download size noticeably.
As for IE itself, I cannot really judge its rendering because VirtualBox doesn't seem to run Windows 10 accelerated, and I think the font rendering in particular suffers from this. I can't say though.
It still has some quirks that need to be worked around. I noticed this particular JavaScript problem.
var xhr = new XMLHttpRequest;
xhr.timeout = 1000;
xhr.ontimeout = function() {console.log('Error')};
xhr.open('GET', '/');
xhr.send();
This throws an exception in IE11. IE only allows timeout to be set between open() and send(). It's allowed to be set at any point per specs, even after send().
https://xhr.spec.whatwg.org/#the-timeout-attribute https://xhr.spec.whatwg.org/#the-timeout-attribute
Microsoft has documentation, from the time of IE8, which clarifies this. Apparently nobody at Microsoft cared to fix this since.
> The timeout property may be set only in the time interval between a call to the open method and the first call to the send method.
https://msdn.microsoft.com/en-us/library/ie/cc304105.aspx https://msdn.microsoft.com/en-us/library/ie/cc304105.aspx
So I tried to report this as a bug. IE doesn't have a public bug tracker, only what appears to be a way to send "suggestions" to the IE team. I read a few of them. There is little activity. You basically only get a formal PR-like response.
Microsoft still has much work to do.
- MichaelGG 12y agoWindows 10 introduced a major VM-screen-breaking bug a few builds ago. Screens can't be sized properly anymore. And acceleration seems to be broken (at least, I hope so, otherwise there's a huge perf regression). Users of VMware and VirtualBox are complaining. Posts to the forums get "answered" by idiot moderators that insist this is a VMware problem (despite VirtualBox not being made by VMware). VMware says MS broke the APIs for screen resolution and they won't fix and hope MS does. OTOH, VMware Workstation is pretty much an end-of-life product with no real updates in quite a while. Overall, it's bizarre. You'd think that in a beta, usage in a VM would be really high, leading to not having regressions on such common "hardware".
- bsclifton 12y agoI have reported several bugs using this UI: https://connect.microsoft.com/IE/feedback/ https://connect.microsoft.com/IE/feedback/ If you didn't already submit the above, I'd recommend you try. I've had my items looked at (you get status updates) within a month of posting it (yeah, not the best turn around, but far from the worst) The IE folks are pretty responsive on Twitter also, with https://twitter.com/IEDevChat https://twitter.com/IEDevChat