{"id":3432,"date":"2017-03-05T15:43:54","date_gmt":"2017-03-05T14:43:54","guid":{"rendered":"https:\/\/en.florianbrinkmann.de\/?p=3432"},"modified":"2020-02-09T10:59:55","modified_gmt":"2020-02-09T09:59:55","slug":"wordpress-weekly-recap-9-browser-support-of-the-new-editor-and-more","status":"publish","type":"post","link":"https:\/\/florianbrinkmann.com\/en\/wordpress-weekly-recap-9-browser-support-of-the-new-editor-and-more-3432\/","title":{"rendered":"WordPress weekly recap #9: browser support of the new editor and more"},"content":{"rendered":"\n

The editor team thinks about which IE versions the new editor should support, and which fallback should be provided to users with non-supported browsers.<\/p>\n\n\n\n\n\n\n\n

Core<\/h2>\n\n\n\n

The new editor and browser support<\/h3>\n\n\n\n

There were some discussions around the new editor and browser support (in short: should the support for IE8 to 10 be dropped or not), and Jonathan Desrosiers attempts to summarize these in his post \u00bbThe New Editor and Browser Support<\/a>\u00ab and to provide some browser usage data.<\/p>\n\n\n\n

There are various reasons for using an old browser: The user only has an old Windows version and uses the default browser, company requirements, and more. Data from different sources say that IE8 to 10 have 0.9 to 2.5 percent, which can be tens or hundreds of thousands people in the WordPress context. So if the team drops the support for these browsers, they need to provide a fallback. There are currently three possibilities (quoted from Jonathan\u2019s post):<\/p>\n\n\n\n