Re: Microsoft made quit the changes to Internet Explorer in Update 1
It shouldn't be that IE should fix "itself", because it's mostly not their fault.
It's the websites that are crappy, and they should be the ones fixing.
MS is doing the right thing here and makes me as a Web dev and a WP user happy. Webkit, specifically mobile Safari, is pretty much the standard the mobile web works on these days. If IE and Safari both work the same, that saves valuable testing and development resources that could be used doing other things. As a web developer, that makes me happy. As a user, I want the sites that I visit to look good and work as expected.
Just to give you an idea what kind of a pain in the behind this can be for developers, this is how you would close a full-screen image viewer in a sane world. It's one simple line:
document.exitFullscreen();
This is how I had to do it in a real-world project:
function exitFullscreen() {
if (document.exitFullscreen) {
document.exitFullscreen();
}
else if (document.mozCancelFullScreen) {
document.mozCancelFullScreen();
}
else if (document.webkitExitFullscreen) {
document.webkitExitFullscreen();
}
else if (document.msExitFullscreen) {
document.msExitFullscreen();
$lightbox.detach();
// MS-only hack for IE11
$(
'body').append($lightbox);
}
}
Designers love to use the newest, coolest effects and features, and this is a very simple example of how non-standardization makes things worse. I have to test for each browser and notice which browser requires extra shenanigans to work properly.
Here's the other thing: I care about IE11 because it's half our IE traffic. I don't care much about WP (even though I use a WP phone) because it's 0.25% of our total traffic. I wouldn't have put that ugly hack in if it was a WP-only issue. Now I don't need to worry. If I can support mobile Safari, WP should work. This is good for devs and users.