v0.5.0

Breaking changes

• Constant DefaultStickyStackName is renamed to StickyStackDefaults and has become an object containing a lot of configurable options. Read more.

Features

• #39: The z-index of each sticky element is configurable now

Fixes

• #42: The demos are up and running

This release includes many more improvements made primarily by @phazei! Read more in this PR: #45

v0.4.2

Fixes

• #31: Bottom anchored sticky was not sticky when at top of page (window.scrollY = 0). Fixed in PR #32 (Thanks to @dotKev)

v0.4.1

Fixes

• #25: The directive is no longer rendered using a template (c05e140)

v0.4.0

New features

• #5, #18, #22, Due to popular request (but also because it was claimed in the repo), jQuery is no longer a dependency. This makes it a truly native Angular plugin.
• #23 Added alwaysSticky flag to make sure a sticky element remains sticky no matter what (docs)

v0.3.0

New features

• #16 Added enable flag to toggle sticky behavior (docs)

v0.2.4

Bugfix

• #12 hlSticky had variables which values couldn't be assigned using scopes. Those include usePlaceholder, anchor, container, stickyClass, mediaQuery, offsetTop, offsetBottom, collection, collectionParent.

Improvements

• Full unit test coverage for hlSticky

v0.2.3

Bugfix

• When the scope of a hlSticky directive was destroyed, it destroyed the entire collection it was part of instead of only removing the element from the collection (wasn't fixed before well enough in version 0.2.2)

v.0.2.2

Bugfix

• When the scope of a hlSticky directive was destroyed, it destroyed the entire collection it was part of instead of only removing the element from the collection

v0.2.1

Bugfix

• The custom class was added to the sticky element when it becomes sticky just after the placeholder was added. This caused the the placeholder to assume the wrong height sometimes.

v0.2.0

New features

• Bottom anchors are now supported
• Events have been introduces. To read more about this check out the demo page.

Improvements

• #7 Angular resolves to every 1.* version when installing the plugin with Bower
• Installing using NPM is described in the documentation
• Added a description and keywords to the package.json file. This way it ends up nicer on the NPM page