$(settings.contentID).offset.left is missing its parens on offset (eg. $(settings.contentID).offset().left)

The userAgent sniffing utilised in this API will cause false positives for Opera 6-8, as those builds ape Internet Explorer builds.

UserAgent sniffing is a thoroughly disproved anti-pattern; please stop using it.

Details of this practice can be found via the following link:

http://www.fortybelow.ca/hosted/comp-lang-javascript/faq/notes/detect-browser/

which is an excellent article written by Richard Cornford, and has stood the test of time.

Furthermore, the assertion of Graceful Degradation for IE < 8 is simply false. Shutting out browsers based upon a very shallow criterion is anything but graceful.

Hi, great Plugin, but just have one problem, when the sticky sidebar starts scrolling its margin-left property changes to the width of the main content on the left side. (My sidebar is on the right). But originally my sticky sidebar had a 20 pixel left margin and that goes away messing up the design, is there a way i can just add those extra 20px to the sidebar margin. Maybe this would make for a good new and easy feature to implement?

@mojotech
I'd like to apply sticky mojo sidebar sticky from bottom of page (not from top of page),
Just like the way google plus do with second column.
https://plus.google.com

Is there any way for doing this using stickymojo plugin ? :)

Position: fixed is notoriously buggy in mobile browsers, does the plugin address that at all?

Thanks!

In the checkSettings() method settings[key] evaluates as false when offsetTop is 0.

the whole block of code

  for (var key in settings) {
       console.log(settings[key]);
       if (!settings[key]) {
           errors.push(settings[key]);
       }
  }

seems unnecessary since the only reason a setting would be false is on purpose since the all have defaults.

Using margin-top seems like it isn't the ideal way to specify where position: fixed starts getting applied, since this requires styling your layout with the sidebar initially pushed down the page if you want it to be spaced from the viewport edge when scrolling. I feel that forcing margin-top is quite restrictive and isn't very flexible (eg: My sidebar is under a header which provides the top spacing, but the sidebar itself NEEDS margin-top: 0; to line up with it's associated main content).

A possible solution would be to use the "top" value instead of "margin-top" since this usually wouldn't affect the initial element positioning when position: static is applied (afaik).

Alternatively it could be nice to have an optional parameter for "additional top viewport offset" when the function is called, which would keep the sidebar this far from the viewport edge even if the top margin is initially set to 0.

I imagine the same could be true for the bottom values, however isn't immediately apparent since it usually won't affect the initial styling.

My project requirements stipulate that certain user actions on the page will append or remove certain content to/from the floating box, changing its height dynamically. It appears that stickyMojo's upper and lower scrolling bounds are thrown off when this occurs, leading me to believe that some recalculation of positioning is required when the box content changes. I see no relevant function to do this, though.

Hello,

I have inherited an MVC project from someone and that someone left the company before I started working at this company. He used stickyMojo and I am having an error as follows: How do I resolve it? Thanks.

Unhandled exception at line 11, column 7 in http://localhost:/Content/js/stickyMojo.js

0x800a138f - JavaScript runtime error: Unable to get property 'top' of undefined or null reference