5 Ways to Make Your Site Rock on the Modern Web (…and Microsoft Edge too)
Edge is Microsoft's new web browser sporting a new rendering engine – EdgeHTML – and an underlying OS to boot in Windows 10. Since upgrades from Windows 7, 8 and 8.1 will be free for most, you can expect a huge influx of Edge users hitting sites in the coming months. Edge is a departure from the past, actually to complete rewrite from past versions of Internet Explorer and I’m sure many web devs will welcome that. With that in-mind, I wanted to share five ways in which you can prepare your site for modern web interoperability and also test for Microsoft Edge in parallel.
#2: Avoid CSS PrefixesCSS prefixes are used by browser vendors to implement new, emerging CSS features before they have been fully ratified by the W3C. If a vendor implements a CSS prefix, it will look something like the example below (this is an IE-specific implementation of the 'hyphens' feature to hyphenate text across multiple lines):
-ms-hyphens: auto;It's really common for sites to have missing vendor-specific prefixes, or have implemented vendor-specific prefixes when they are not required in common CSS properties. This may cause a webpage to render incorrectly in Microsoft Edge or other modern browsers. Browser vendors are using prefixes much less now because of the management problems associated with them. Some browsers, Microsoft Edge included, rarely if ever use prefixes at all. Where possible, avoid the use of vendor-specific prefixes. However, if you absolutely must use vendor prefixes, use Grunt PostCSS to automate the management of prefixes within your CSS.
#4: Become Plugin FreeEdge doesn't support plugins, so it's a good time to consider how to move away from proprietary plugins like Flash and Silverlight. Edge does support Flash, but rather than using a plugin architecture Flash is delivered with the browser, and is updated and patched centrally by the Edge team in collaboration with Adobe. For some sites, moving away from plugins is pretty straight forward. However, many sites will find this difficult, particularly those that are delivering media content. The Edge team have provided guidance on how to move to HTML for premium content over on the Edge Blog.
#5: Ensure Edge Rendering ModeIf the <!DOCTYPE> directive is missing or doesn't specify a standards-based document type, Edge may incorrectly display your page. The scanner runs a simple test to determine that your site is set up correctly, so enter your site URL and find out quickly if it passes. If you want to see what the actual test looks like, you can view the code for the scanner over on GitHub.
- Announcing the latest improvements for the F12 developer tools in Windows 10
- Technical sessions on our new browser, Microsoft Edge
- Web development talks from Build 2015
- Scan your site for out-of-date libraries, layout issues, and accessibility
- Use virtual machines for Mac, Linux, and Windows
- Remotely test for Microsoft Edge on your own device
- Coding Lab on GitHub: Cross-browser testing and best practices
- Woah, I can test Edge & IE on a Mac & Linux! (from Rey Bango)
- The Edge Rendering Engine that makes the Web just work (from Jacob Rossi)
- Unleash 3D rendering with WebGL (from David Catuhe including the vorlon.JS and babylonJS projects)
- Hosted web apps and web platform innovations (from Kevin Hill and Kiril Seksenov including the manifold.JS project)
Great 5 points – easily overlooked.
Really usefull tips! Many thanks Martin!
Thank you Martin for sharing this useful information. I think for those sites that are delivering media content, moving away from plugins will be difficult.
This is a great post Martin! Thank You so much for sharing these tips. Quite helpful.
Updating JS libraries always work when it comes to EDGE. Thanks for sharing other tips martin.
Hi Martin, thanks so much for sharing this. Its really useful for me and my team.