One of the great things about our industry is how passionate people are about helping each other learn. Be it articles about the latest and greatest techniques that they’ve discovered, or blog posts about new web platform features that have landed in modern browsers. All this content–often created by people in their spare time–has one downside: it is often unmaintained, and with the frequency that certain features or APIs can change syntax or new prefixed implementations arrive, the content can become outdated. If the content appears high up in search results, or is linked from influential sources, it can lead to developers copying code that may not work in as many browsers as it could. It can also harm the adoption of the latest version of the spec.
With the introduction of IE11, all major browsers now support the Fullscreen API. However, due to prefixes and differences between the specification and early implementations, you may need to update any code you have that makes use of this feature. When I looked through the top search results on Google, none of the results showed both the latest syntax for all features and the ms prefix. In this post I’ll show you what has changed and what needs updating.
While most CSS features are defined by the CSS Working Group and either included in CSS Level 2.1, or individual CSS Modules, there are a surprising number squirrelled away in various other specifications. These may or may not have been worked on in conjunction with the CSS WG, but as many probably get overlooked, I thought I’d list them in a blog post so that I can find them later. How many did you know about?
In this review of Internet Explorer 11, I’m going to attempt to ascertain if it can actually be considered a modern browser.
There has been much written about IE since Microsoft allowed to to stagnate with IE6. There have been a number of jokes written about IE; you probably reconigse them, as they are hardly original and get repeated ad nauseam. There is the one about how slow IE is, then how unpopular it is, and then the one about downloading [insert the favourite browser de jour here]. Then there is the revisionism about IE6. Yes, it actually was a good, and popular browser. when it was released.
But, do the popular perceptions about IE still hold up today, or are they as outdated as those about memory management in Firefox, or that Opera (who boasts a quarter of a billion users on mobile alone) has no users? Read on to find out.
However, some platforms use web technologies for native apps. As such, the platform vendor has probably had to solve this problem using those tools. One such platform is Windows 8. Internet Explorer 10+ provide a bunch of vendor specific CSS properties for touch-based scrolling. As these have proven useful, the properties for scroll offsets have been recently been added to the standards track as Scroll Snap Points. In this post, I will quickly guide you through the functionality that is currently in the spec. As it is very new, everything is subject to change, but it does work as is in IE 10 and 11.