101–110 of 247 posts
Earlier quoted context omitted.
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.
- Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version.
- Decouple the browser from the operating system. I don't really care if they make it cross-platform (though it would be nice), but if the browser stops updating unless you upgrade to the next version of Windows you WILL end up with legacy sites again and again that cater to a specific version, and then we can start over and just replace every rant against IE 6-7-8 with Spartan 1-2-3.
Earlier quoted context omitted.
I just wished we could put on top of our HTML something like: or something along those lines.
We just need to implement an HTML renderer (or two or three) in JS and then ship the renderer with your site.
Hahaha. Microsoft and Internet are fundamentally incompatible. All you need to do is go to their homepage to see they don't get the Internet. Never have, never will.
http://rainypixels.com/words/the-story-of-the-new-microsoft-...
I really really hope Microsoft adopts the strategy from competing browsers: - Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version. - Decouple the browser from the operating system. I don't really care if they make it cross-platform (though it would be nice), but if the browser stops updating…
I really really hope Microsoft adopts the strategy from competing browsers: - Make one version of Spartan and keep it AUTO-UPDATED, instead of shipping a new version every couple of years that is, more or less, completely decoupled from the previous version. - Decouple the browser from the operating system. I don't really care if they make it cross-platform (though it would be nice), but if the browser stops updating…
This is what IE 11 currently does, so I would imagine they will continue doing so with Project Spartan.
I hope those 9,000 sites include github. IE hangs when confronted with a github display of a PR that has more than 1000 lines of diff's.
> 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.
Earlier quoted context omitted.
We just need to implement an HTML renderer (or two or three) in JS and then ship the renderer with your site.
Bingo :) But it makes me wonder how well is asm.js supported by the new IE?
Earlier quoted context omitted.
We have a already have lot of competition. In fact, it's never been better: Chrome, Firefox, WebKit, Chromium, Opera. You can even get the source code for Firefox and Chrome and contribute. I'm glad Microsoft is making a better go at it, but honestly, Microsoft could have built a more compliant browser any time they wanted too. https://html5test.com/results/desktop.html
Chrome and friends aren't webkit anymore, but only by way of forking. Otherwise Chrome, Chromium and Opera 15+ are the same engine. The family tree kind of looks like this: -- Internet Explorer -- Firefox -- Safari \ -- Chrome, Chromium, Opera 15+ -- Opera 12 (abandoned) I'm a little unclear on how differentiated Webkit and Blink are in practice, but sadly we have only 3.5 major engines competing at this point.