Updated to use
on instead of
bind, because of this LavaLamp now requires jQuery 1.7 or later.
This release provides a fix to a longstanding bug (noLava elements with additional classes), callbacks and customizable class names
focusoutto support keyboard usage
hoverStart, hoverFinish, returnStart, returnFinish: callbacks for different stages of the hover process.
selectClass, homeClass, skipClass: optional overrides for internally used classes
This release sees a major change to the hover
.backLava element, namely, margins and padding are forced to zero. This is to properly support the new
containeroption allows changing the container for the hover
.backLavaelement to any valid DOM element. The default setting is '' or an empty string. If left unset, the value of the
targetoption will be used. See the new multi-layer demos for examples.
includeMarginscode option causes the hover element to expand to include the margins of the target element. Default for this option is
false. See the last multi-layer demo.
containerfeatures. To correct this, LavaLamp now forces
padding:0on the hover .backLava element. While this did not effect demos on this site, you may need to adjust your .backLava CSS to work properly with this version by adjusting the CSS padding and margins on your target elements.
Note: If you find a bug, have a feature request or better yet, a pull request, please submit an issue and let me know what you've found.
Finally out of beta - sorry for the long wait, and thanks for the feedback.
targetoption allows changing the target element from
lito any valid jquery selector. See target demo
returnDelay, refined internal variable usage.
lidimensions, including both elements' all four border sizes.
mouseleave/mouseenterto bind events so LavaLamp should continue to work with jQuery 1.2.3 onward.
returnDelayto fix errors some were seeing - thanks to Michel and Richard for noticing this.
mouseenter/mouseleaveto fix jerky/stuttering animation problem when using large margins on
<li>elements. Thanks to Thomas for the solution and Chris for clearly demonstrating the problem.
noLavaclass detection to prevent LavaLamp effect on
<li>elements with this class. See the demo page for details.
$references inside plugin to work correctly with
.selectedLavafor clarity and improved support
autoReturn: true- if set to false, hover will not return to last selected item upon list mouseout.
returnDelay: 0- if set, will delay auto-return feature specified # of milliseconds.
setOnClick: true- if set to false, hover will return to default element regardless of click event.
homeLeft: 0, homeTop: 0- if either set to non zero value, absolute positioned li element with class .home is prepended to list for homing feature.
homeWidth: 0, homeHeight: 0- if set, are used for creation of li.home element.
returnHome: false- if set along with homeLeft or homeTop, lavalamp hover will always return to li.home after click.
startItemwhen you upgrade!
linumparameter created a nifty out-of-bounds fly in effect that several people requested as a feature, so the home features are born!
width- I opened a ticket here: http://dev.jquery.com/ticket/3881 but no one seemed interested in fixing it at the time. UPDATE: John marked this as FIXED in the jQuery 1.4 core and later as of 2009-12-05; see link above for details.