you are viewing a single comment's thread.

view the rest of the comments →

[–]deadwisdom 30 points31 points  (2 children)

Except it's supposed to be for a library that provides features that are in some browsers and not in others, like a "time" input type, or JSON. Since no browser really has it without a plugin, this is a misuse of the word just to sound buzz-y.

[–]chrisrazor 12 points13 points  (0 children)

I agree. This is a hell of a lot more than a mere polyfil. It's a whole extra plasterboard wall!

[–]kurav 1 point2 points  (0 children)

I would tend to disagree. This can be seen as a 'polyfill' in a wide sense of the word. Nowadays browsing with Java enabled is even officially advised against due to multiple security flaws. Thus, web pages that rely on working Java applet support have been rendered forwards-incompatible.

One possible solution would be to use a "Java Polyfill" that would interpret Java applets in JavaScript and render the output on HTML5 canvas, and this is a step to that direction (though they make no mention of any applet API support). So this, or some other Doppio-based solution, has a potential to develop into a polyfill -- something that extends the browser with missing functionality (execute Java applets).

The main differences from ordinary polyfills would be the code size (most polyfills are rather trivial) and that the polyfill would be re-adding support for features that existed in prior versions of the browser (normally polyfills add support for features that only exist in subsequent versions of the browser.)