Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
83 lines (57 sloc) 2.81 KB
EZ-Sticky-Footer jQuery plugin
Version: 0.1.2
jQuery plugin to make the page footer stick to the bottom of the page.
Copyright (c) 2013-2014 Marat Nepomnyashy maratbn@gmail
Licensed under BSD-3
JavaScript-based solution for a non-trival CSS problem.
* No numeric configuration with dynamically-changing and arbitrary
footer / content areas heights.
* No absolute or relative positioning.
* No other funky CSS tricks and hacks, in fact no CSS required.
* Works on IE6+.
* Works on the default Android Browser.
The plugin requires that several <div>s (or any other tags that are
displayed in block mode) be designated as:
(1) Main page container <div>
(2) The content expander <div>
(3) The page footer <div>
The <div>s are designated by assigning them special CSS class names
according to the following table:
role CSS class name to assign
---- ------------------------
page container jq-ez-sticky-footer-page-container
content expander jq-ez-sticky-footer-content-expander
page footer jq-ez-sticky-footer-page-footer
The structure of the page must be the following:
<div class='jq-ez-sticky-footer-page-container'>
<div>your header (does not need any CSS class)</div>
your content (does not need any CSS class)
<div class='jq-ez-sticky-footer-content-expander'></div>
<div class='jq-ez-sticky-footer-page-footer'>
your footer
(1) The container <div> designated for use by the plugin should
not have any customized margin or padding styles applied to
it, as the plugin needs to manipulate these settings for it to
work. If needed by the page, these settings can still be
specified in a nested <div>.
(2) The expander <div> must be inside the page content <div>.
(3) The expander <div> must be completely empty.
Please see INSTALLATION_INSTRUCTIONS for more details.
If the plugin does not seem to work correctly, please file a bug report
When filing a bug report, please make sure to state the browser you're
using, and to include links to 'example.html' on your webserver, as
well as the page on which the plugin is deployed but does not seem to
be working.