Bregalad wrote:
Windows version of Safari
Discontinued. I get the impression that when it did exist, it was intended to help web developers become familiar enough with Safari to develop web apps for iPhone OS 1, where all apps were expected to be web apps.
tokumaru wrote:
Also, JavaScript libraries that abstract the browser differences (such as jQuery or the multitude of polyfills that transparently simulate new functionality in older browsers) are very helpful.
If you see a problem on a specific browser but not on another, is there a bug in your script for relying on unspecified or undefined behavior? Or is there a bug in the polyfill?
Quote:
The fact that new browsers (and software in general) auto update by default surely helps with achieving a consistent experience across different platforms.
This wasn't true prior to April 2014. Internet Explorer for Windows XP was widely used, and Microsoft refused to update it past version 8. In April 2014, Microsoft stopped issuing security updates for Windows XP, which means you can finally presume that IE on XP is insecure.
Quote:
There are also online services that run your website through several different browsers and show you the result. Sure, there's only so much you can verify from looking at static screen captures, but since the bulk of browser incompatibilities lie in the CSS, static images are usually enough.
This is true of the
-webkit- prefix hell. But a lot of times one will run into a polyfill bug, an unusably slow polyfill, an intentional refusal of a particular operating system publisher to allow distribution of browsers that implement web platform features required to create a polyfill, a failure to respond to touch events that you can't generate with a mouse on a PC browser, or a failure in interactive technologies such as the 2D canvas or WebGL. For example, Safari for iOS prior to iOS 8 would consistently refuse to render WebGL outside Apple-approved iAd modules.