Animate On Scroll (AOS) vs. JavaScript vs. Polymer vs. jQuery Comparison Chart

Animate on scroll library. In order to make it work, you'll have to make sure your build process has configured styles loader and bundles it all correctly. If you're using Parcel, however, it will work out of the box as provided. AOS object is exposed as a global variable, for now, there are three methods available. Initialize AOS, recalculate all offsets and positions of elements (called on window resize), reinitiate the array with AOS elements, and trigger refresh (called on DOM changes that are related to AOS elements). By default, AOS is watching for DOM changes and if there are any new elements loaded asynchronously or when something is removed from DOM it calls refreshHard automatically. In browsers that don't support MutationObserver like IE, you might need to call it by yourself. You can also tell AOS to trigger a custom event on a specific element. You can also add custom animations.

The Polymer library provides a set of features for creating custom elements. These features are designed to make it easier and faster to make custom elements that work like standard DOM elements. Similar to standard DOM elements, Polymer elements can be instantiated using a constructor or document creation element, configured using attributes or properties, populated with internal DOM inside each instance, responsive to property and attribute changes, styled with internal defaults or externally, and responsive to methods that manipulate its internal state. Registering an element associates a class with a custom element name. The element provides callbacks to manage its lifecycle. Polymer also lets you declare properties, to integrate your element's property API with the Polymer data system. Shadow DOM provides a local, encapsulated DOM tree for your element. Polymer can automatically create and populate a shadow tree for your element from a DOM template.