News for hackers. Stuff that matters.
Re:Documenting the Web together by frik on Thursday October 19, 2017 @12:50AM (#15505550)
"One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering."

Many sites already don't work correctly in Edge, IE11 nor Firefox - it's too late, these are minor browsers, used by a smaller fraction of end users. End users on on smartphones use 95% a WebKit originated based browser aka Chrome/Safari. Chrome and Safari are bigger than the rest on desktop.

Sites in 2017 are tested against Chrome and Safari by web developers.

http://gs.statcounter.com/browser-market-share/desktop/world...

http://gs.statcounter.com/browser-market-share/mobile/worldw...

Re:Documenting the Web together by epse on Thursday October 19, 2017 @01:20AM (#15505637)
Minor is very relative here, especially with regards to Firefox. IMO anyone who only tests against Chrome and Safari is seriously wrong. The amount of features not supported by Firefox or Edge are relatively small and so basically everything except for a few special cases should just work everywhere.
Re:Documenting the Web together by TazeTSchnitzel on Thursday October 19, 2017 @08:00AM (#15507132)
Chrome descends from WebKit, but it isn't WebKit. As I unfortunately learned recently when a workaround for a WebKit bug broke modern Chrome.
Re:Documenting the Web together by foxylion on Thursday October 19, 2017 @02:45AM (#15505925)
It depends on the user base. Customers of the company I work for mostly use IE or Edge and only Chrome because we highly suggest it. Without decent IE/Edge support we would have less customers.
Re:Documenting the Web together by disiplus on Thursday October 19, 2017 @02:19AM (#15505821)
lol sure,

from analytics

chrome 38.17%

safari 20.30%

firefox 17.10%

ie 15.56%

edge 7.08%