[deleted]
The birth of Microsoft's new web rendering engine
81–90 of 247 posts
Re: The birth of Microsoft's new web rendering engine
#82I'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 someth…
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
#83> the new engine began as a fork of MSHTML.dll but has > since diverged very quickly Curiously, this means that Spartan will still be able to trace its lineage back to 1992's NCSA Mosiac (in contrast to Mozilla's Servo, which is a greenfield project). I expect that it will be fascinating to compare the two projects as each matures.
To be pedantic: even if there is code from MSHTML.dll in Spartan, there's no code from NCSA Mosaic in MSHTML.dll. Internet Explorer originally licensed Spyglass Mosaic , which licensed the name (and the code) from NCSA, but did not actually use any of the code. Though I suspect that there's not actually any Spyglass Mosaic code left in IE these days. (Edited, I said that there's no MSHTML.dll code in Spartan. That I…
Internet Explorer 1.0's "About" box claims it is "Based on NCSA Mosaic": http://utilu.com/IECollection/img/iecollection_ie100_win40nt...
(Curiously, Internet Explorer 1.0 showed a version number of "4.40" in the about box.)
Re: The birth of Microsoft's new web rendering engine
#84Earlier quoted context omitted.
Honestly, with as much OSS as they've been putting out there recently, I wouldn't be surprised to see this browser go that route too. Maybe.
They can't. They said in a court of law that IE can't be separated from Windows.
The actual court case you're referring to has to do with the bundling of IE with Windows and how it can't be pulled out. Remember that IE actually used to be cross-platform until version 5 with IE for Mac although it used a different rendering engine (Tasman vs Trident).
Re: The birth of Microsoft's new web rendering engine
#85Earlier quoted context omitted.
I understand the language. I don't understand what they mean by "patterns". Common edge cases where js/css/html is broken in specific ways? If you write html/css in a relatively compliant way, things will not be so broken that a browser vendor needs to account for them in a "long tail". If your js is broken, well tough luck. Are they just talking about how to implicitly handle commonly malformed HTML, as all browsers…
If people in the past have written bad js which worked in IE, Microsoft aren't now going to break that code. They don't consider saying "tough luck" to businesses with code which works for them today acceptable.
my problem is they're selling this as a "clean break" with no baggage. but then in the same breath explain how they've found a way to still accommodate that baggage and calling it a "long tail".
IE is still gonna live next door (to be used for enterprise/compat) probably for a while. I don't understand what they are saying about solving incompatibility issues of IE-specific code in Spartan - which is presumably NOT IE.
Re: The birth of Microsoft's new web rendering engine
#86So fun thing to do in these kinds of videos is to look for women. FYI. This video has 1 woman, at the end. She doesn't say anything, she just stands there, and she's only visible for a few seconds. Summing up. Microsoft's new engine, still fighting to gain traction with 50% of the population ;)
So you believe web browsers should be tailored to a specific gender? What would a woman-friendly web browser look like? Does it open a thousand URLs before finally picking which one to render?
Re: The birth of Microsoft's new web rendering engine
#87YES! 1-2-3-4, I declare a browser war! Finally. This is the Microsoft I've been waiting for! No more rolling over and no defeatist talk of adopting WebKit or whatever. Microsoft is going to use its muscle and position to make a truly competitive browser. We need more competition, and we need the default browser in Windows to be just as good as Chrome and Firefox. Microsoft, I hope you pull every -ms- vendor flaggin',…
Why the fuck did anyone ever think vendor prefixes are a good idea? If you want to prefix, prefix with versions. I should be able to type `-beta-mask-image: url()` and any browser that implements that version of the spec can pick it up. There's no good reason to have to type the same exact thing 3 times to target each browser engine.
It's better than typing one thing and it doing 3 different things in 3 different browsers.
Re: The birth of Microsoft's new web rendering engine
#88@IEDevChat on twitter is now (and for the next two hours) answering questions regarding Internet Explorer and Project Spartan. Just ask your question(s) with the hashtag #AskIE.
Re: The birth of Microsoft's new web rendering engine
#89Earlier quoted context omitted.
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
the point is you should be doing feature tests, not browser tests.
there's no such thing as a feature test on the server side.
Re: The birth of Microsoft's new web rendering engine
#90Earlier quoted context omitted.
Why the fuck did anyone ever think vendor prefixes are a good idea? If you want to prefix, prefix with versions. I should be able to type `-beta-mask-image: url()` and any browser that implements that version of the spec can pick it up. There's no good reason to have to type the same exact thing 3 times to target each browser engine.
It's better than typing one thing and it doing 3 different things in 3 different browsers.
No, that just shifts the burden onto every website instead of onto the few browsers. If they render differently someone needs to fix their browser rather than everyone has to build sites that work both ways.