News for hackers. Stuff that matters.
Re:The birth of Microsoft's new web rendering engine by FreakyT on Thursday February 26, 2015 @12:44PM (#9113822)
I'm glad to see that Microsoft is finally ripping out all the weird legacy modes -- IE11 essentially ships with 6 different rendering engines! [1]

* IE5 (quirks mode)

* IE7 (compatibility view)

* IE8, IE9, and IE10 (available from the x-ua-compatible meta tag)

* IE11's actual rendering engine

As an aside, the hilariously long user-agent string is perhaps the best evidence that string-based browser detection is something that web devs should avoid at all costs. It manages to include "Safari", "Chrome", "AppleWebKit", "KHTML", "Mozilla", and "Gecko".

[1] https://msdn.microsoft.com/en-us/library/dn321432.aspx

Re:The birth of Microsoft's new web rendering engine by spain on Thursday February 26, 2015 @02:32PM (#9114804)
>As an aside, the hilariously long user-agent string is perhaps the best evidence that string-based browser detection is something that web devs should avoid at all costs. It manages to include "Safari", "Chrome", "AppleWebKit", "KHTML", "Mozilla", and "Gecko".

Further reading:

http://webaim.org/blog/user-agent-string-history/

Re:The birth of Microsoft's new web rendering engine by hughes on Thursday February 26, 2015 @02:56PM (#9115017)
For the lazy, the new UA string is:

Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0

Glad I don't deal in server-side analytics!

Re:The birth of Microsoft's new web rendering engine by bzbarsky on Thursday February 26, 2015 @03:11PM (#9115133)
It's basically the Chrome 39 UA string with "Edge/12.0" added to the end so people who really care can tell it's not really Chrome....
Re:The birth of Microsoft's new web rendering engine by eyeareque on Thursday February 26, 2015 @10:38PM (#9117038)
I'm sure the reasoning behind those modes is because they had big (paying) customers who needed them there to help their "never ever getting an update" mission critical system webpages continue to work properly.
Re:The birth of Microsoft's new web rendering engine by leeoniya on Thursday February 26, 2015 @12:54PM (#9113895)
if you're not detecting on the client (via javascript), then you have to rely on headers. well, maybe via IE conditional comments + cookie setting on transparent pixel request
Re:The birth of Microsoft's new web rendering engine by stephenr on Thursday February 26, 2015 @02:41PM (#9114879)
the point is you should be doing feature tests, not browser tests.
Re:The birth of Microsoft's new web rendering engine by exprE on Thursday February 26, 2015 @03:30PM (#9115261)
In an ideal world, perhaps. Sadly, in the real world, a browser seemingly supporting a feature doesn't mean it gets it right, and not all features can be detected by testing.
Re:The birth of Microsoft's new web rendering engine by leeoniya on Thursday February 26, 2015 @03:27PM (#9115242)
there's no such thing as a feature test on the server side.
Re:The birth of Microsoft's new web rendering engine by stephenr on Friday February 27, 2015 @03:27AM (#9117806)
The things that are different are almost exlusively related to client side tech- html, css and js.