Feature to scroll the viewport to display the menu

Fix a problem with border inside table

Fix style path

Less strict PropTypes for string placeholders to optionally allow React nodes

Remove the warning without modifying the functionality by using

React.PropTypes.oneOfType...

changed LayoutItem.i property to be of type "string" instead of "number"

modified 'synchronizeLayoutWithChildren' method to convert all uses o…

Was referencing default.css which doesn't exist

Fixing a problem where the border isn't showing when the element is inside a table.

Add missing React import

When using this branch, I got a `React is undefined` error. Adding `React` as an import fixed th...

- From `dist/default.css` to `dist/react-select.min.css`

as well as adding the feature to the README

Change input back to div

Async tests

Treats as if the options list was empty

The DOM is still needed for the other tests, and `npm test` may run the async tests
first. This...

Documented in the test case
Changed the cache checking to start with the full search string, and...

+ the first few tests for Select.Async, using the shallow renderer
+ removed redundant asyncOpti...

If a select box was activated near the bottom of the viewport, the
viewport will now shift the m...

This essentially reverts the change made here
https://github.com/JedWatson/react-select/pull/595...

I don't expect pressing Enter on an open menu to bubble back to the Select's container.

Rebase

Fix failing Value.js tests

Fix tests 1.0

These will be re-enabled / moved in a future commit

This is now in the README, so we have fixed the test to match

If the focus is somewhere else on the node, then the blur is ignored.
This makes the "clicking a...

Test patched

This is a hangover from pre-1.0, when the current value was held in the
place-holder, hence thi...

Tests patched

All other props are still passed through

Using the internal ref. This is a bit dangerous, but I can't think of a better way
to do it now.

Not sure if this is the right behaviour, but it does make much of the logic simpler.
It is also ...

onChange now called only with the concatenated value when simpleValue=true

After searching, this left the select box closed, but displaying no value, even though
the value...

Fixed tests to match new behaviour.

After selecting an item in a non-searchable Selectbox, the menu is no longer closed
Tests change...

There are now two ways to pass the value, either as the original object,
or as the value propert...

onChange now called with array of option objects

The test for a single value of 0 was already there, and it caught the bug for the simple
test o...

This is as passed as a prop to `createControlWithWrapper`, but is then removed
This means that o...

When the `value` prop is set to a value not in the options, previously the value
would be shown ...

This is a hangover from the old version where it produced the same result.

These tests were to do with entering and leaving the options, where the
behaviour is now that t...

Fix keyboard nav for non-searchable multi controls

#594 and #589 Fixes navigation issues with non-searchable controls

Update doc for asyncOptions (after replaced with Select.Async)

Thanks @mjackson!