Feature Parity with other Libs

[solomonhawk]

Despite the title, I'm not convinced we need complete feature parity with any other specific datepicker libs.

Thoughts:

Referencing some other datepicker libraries to get a sense for the options they expose. I'm not certain about which of these we want to implement. Further discussion on the direction and philosophy behind Ca11y is required. Discussions in #13 and #20 seems to indicate that there is some interest in having Ca11y not be directly responsible for manipulating DOM outside it's own tree. It may also be nice to allow a user to control into which container the Ca11yndar markup get's rendered (option called render or container)?

Possible Options to Add:

container || render: per above, container could be a string selector or node. render would be a function autoClose: auto hide the datepicker when a date is selected clearButton: display a button that clears the selected date disableTouchKeyboard: no keyboard will display on mobile (call blur on the input when the calendar is shown)

Links:

http://bootstrap-datepicker.readthedocs.org/en/stable/options.html

[solomonhawk]

We want to add these options: container autoClose endDate startDate