Enable dropdown bounds check so it can be guaranteed to be visible when open.

Dropdown will try to honor chosen align setting, unless the resulting position makes part of the dropdown content to be outside of chosen bounds. In that case, the alignment will be automatically update to make the whole dropdown visible in the chosen bounds.
Bounds setting "window" will display the dropdown in the currently visible document area, ensuring the user does not need to scroll to see the dropdown.
Bounds setting "document" may force the user to scroll to see the dropdown.
Turn this behaviour off by setting the "bounds" setting to anything else than "window" or "document".
Typo fix
Fix computation error, add check for left and right dropdowns and introduce container bounds setting
Merge branch 'master' of https://github.com/zurb/foundation into PR-dropdown-fit-bounds
Completely new and optimized algorithm for smart positioning based on preference arrays
fix tab deep-linking
[+]: added a missing class for the fixed "magellan", so we can style it

PS: there was already a "removeClass('fixed')" ;)
add !default to $switch-active-color
Update examples_switch_variables.html
Enable 'info' and 'warning' classes on buttons

Includes these classes in export, along with hover effects and disabled
Update _functions.scss to add !global support.

This should not affect libsass anymore: https://github.com/sass/libsass/pull/409
not instead of == false
Followup: add bg-hover and border-color for info/warning buttons

Missed this in initial commit
404 foundation.css.map not found

When using source maps for chrome and pulling in resources for bower it causes a 404. Adding the css.map file resolves this issue.
Fixed abide email validation

This validation rule ensures that there is a domain suffix. Before "joe@joe" would validate as an email address. Obviously it is not.
Trigger window resize on open

Triggering a window resize event when Reveal opens can help when Reveal contains dynamically created content.
fix bug where every valid element after an invalid was marked as invalid

There is a bug where every valid element after an invalid element was marked/styled as invalid due the fact that the `validations` array was global and always included a `false` when a previous element was invalid.
Off-Canvas Hover background: separate variable.

The background color, which applies when one hovers an off canvas list
item, was hardcoded. This annoyed me. Pushed to a separate var, docs
fixed also.
Ensure all inserted searchTerms are unique
Merge pull request #5740 from doertedev/master

Off-Canvas Hover background: separate variable.