What is polyfil?
Means a code fragment (“interlayer”) that is added to the required place, which is able to implement a separate functionality, but in this case we usually deal with our own API. I meant something that you can just plug in and it will do its job quietly. (Remember the old acquaintance “shim.gif” that required you to insert the image needed to fill in the empty tabular td cells? So I wanted something like this, but working automatically, not requiring my participation.)
And I really like this idea of visualization of how we, so to speak, “repair” the browser. Since the wall itself is flat means you can paint anything on it or stick wallpaper to your taste. At one time I received a review in which the opinion was expressed that “this word needs to be changed”, but at that time the community needed a suitable word as never before, as we once needed in terms like Ajax, HTML5, Web 2.0 – in anything that can denote our ideas. It does not matter that the word is not perfect, it stands firmly on, accepted by the community of developers and designers, and everyone understands its meaning perfectly. In fact, I never deliberately imposed this term, but simply applied it in some key places (mostly in the book) and as far as I remember after a couple (or quite a lot) months, just after the presentation of Paul Irish, in which he directly reflected the word “polyphyl”, this term was widely adopted. (It seems to me that the addition of the page “Modernizr HTML5 shims & polyfill” to this presentation played a significant role.) Definitions.
In my opinion, all of the above was perfectly summed up by Alex Sexton, classifying “poly-peeling” as a form of regressive improvement. Paul (Irish) also describes it as: Shim, which mimics a new, not implemented in the old API browsers, giving them the opposite functionality. A few examples. Here’s an example: the sessionStorage interface is available in all recent browsers (IE8 and later), but is missing in IE7 and below. In order to enable such support in older browsers that do not provide the sessionStorage interface, you can use a polyfill. Now, having a polyfiler available, I, as a web developer, can fully rely on using the session-based Web Storage API and no longer need to test my code further or forking it to handle various situations. Another example that provides canvas (canvas interface) support in IE. Here is the case that really justifies the choice of the term, or rather its first half – “poly-“. In the case where the initial support for the canvas is missing, you can implement it using Silverlight technology. If Silverlight is unavailable, we can drop to VML level, use…
Here is the case that really justifies the choice of the term, or rather its first half – “poly-“. In the case where the initial support for the canvas is missing, you can implement it using Silverlight technology. If Silverlight is not available, we can drop to the VML level using excanvas (however, keep in mind that in fact the excanvas also includes the Silverlight bridge, which, I believe, will be tested first). The use of these two scripts provides developers with a fairly robust foundation for the canvas interface in browsers that lack native support. Conclusion Not so long ago, Paul Irish published a list of available polyfiles and shims — an excellent resource that contains an impressive list of headache remedies caused by our developers with older versions of browsers. Apparently, the use of polyphiles has proven itself well, and it would be nice for you to start using this approach in cases where you need to increase the functionality of old (and sometimes new) browsers to the desired level.