Jump to content

Talk:EdgeHTML

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by SineBot (talk | contribs) at 20:48, 10 February 2016 (Signing comment by Klaas Nekeman - "EdgeHTML only a fork of Trident?: new section"). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconSoftware: Computing
WikiProject iconThis article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.

"Spartan browser rendering engine"

Why are we calling this article "Spartan browser rendering engine"? The engine is called Edge. Simple as that. Microsoft has never referred to this new engine with that as a name.--YannickFran (talk) 20:01, 10 February 2015 (UTC)[reply]

IE to retain old engine.

As it says here, IE and Spartan will have separate engines, I will update the article to reflect the changes. Davidbuddy9 (talk) 00:26, 14 April 2015 (UTC)[reply]

UAS

The UAS is now almost completely different, resembling Chrome more than IE:

Chrome Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36
Edge 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
IE11 Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko

Should we talk about this in the article? To a website that doesn't know about Edge, this looks just like Chrome 39 on Windows 10.  Supuhstar *  18:51, 18 June 2015 (UTC)[reply]

EdgeHTML only a fork of Trident?

It appears to me that Microsoft Edge has completely rewritten the layout engine, replacing components one by one during development. Technically this could be seen as a fork, but in the case of Microsoft Edge so much code has been rewritten that I think the wiki articles mentioning Microsoft Edge browser should not use the term fork. Generally the term fork is used for software that diverted from the original, but keeping most of the older code intact.

In this case the complete rendering engine has been rewritten almost from scratch. I think that Microsoft Edge browser is not just a fork, but a new browser with a completely rewritten layout engine. — Preceding unsigned comment added by Klaas Nekeman (talkcontribs) 20:47, 10 February 2016 (UTC)[reply]