I realize that nowadays this isn't as simple as that, but if we had started along that path, things would be much better now.
But not everyone agrees with you -- the readers want control, too, and it's their hardware, after all.
- Gecko was around before either of WebKit or Blink, so targeting this toward Firefox is getting history backward.
2) That wasn't my point. WebKit derivatives clearly won. Does Firefox even need to also own an engine when their goals seem to be entirely around the browser product?
Adopting Blink would, furthermore, impose a set of design and architectural constraints not necessarily in line with Firefox's priorities as a project. With Gecko they're investing in parallelism and pulling in more and more components from Rust/Servo, for example.
Firefox has been something of an underdog from its inception, releasing at a time when IE had already "won". Chrome taking that spot won't make Mozilla scrap everything and start over—this is familiar territory.
Of course, this is all ignoring the absolute upheaval and loss of momentum a total rewrite on top of Blink would wreak on Firefox as a project.
https://i.imgur.com/zPHcYL3.png
And searching for Proxy gives me all of these options:
Root for other browsers, sure.
But Microsoft's? No.
They wantonly abused their market position in the 90s & stalled the advancement of the web for years.
There many other worth products to cheer for rather than the latest offering from a habitual bad actor.
The real problem is this is still webkit/blink and ultimately control still goes to google.
It also seems to suffer from the same weird font rendering as a lot of Metro apps.
The thing that really drove me nuts was how the address bar jumps around when you're trying to select part of a URL, which makes it so much harder than it ought to be when you are trying to click and drag with a mouse, let alone a touch interface.
Jumping address bar? Ohhhh yeah hate that one: https://twitter.com/LincolnAtkinson/status/88703561300998963...
MSFT has new leadership and is cooperating much with open platforms more than ever before. Let's encourage that.
Edge still has a spoof referrer header vulnerability that's been known for more than 6 months now: https://www.brokenbrowser.com/referer-spoofing-patch-bypass/
More generally, there's a lot more to making the web great than a blind sprint to adopt every API. Just because it isn't shipping doesn't mean Microsoft isn't a (very) active participant in the standards conversations, testing behind flags, etc. That is a huge part of moving the web forward.
Take Grid as an example - we were the last browser to ship the updated spec, so you could say we "held it back." But we also originated the first version of the spec and worked closely with the community, standards bodies, and other browser vendors on making sure what ultimately shipped cross-browser this year was great, useful, and interoperable. Is that holding the web back?
(Disclaimer: Edge employee)
I've never used Edge and have no particular interest in it, but html5test is basically a way for Chrome users to feel good about themselves.