Fixed bug that left a '-1' tabindex on a select after destroying selectize

Selectize sets a '-1' tabindex on the original select element when
initialized. When the select element did not originally have a tabindex
set, Selectize would not properly remove the '-1' tabindex when
destroying itself.
Changed tabs-as-spaces to just tabs
Reverted changes to files in the dist folder

Because I just read the notes for contribution in the README.
Changed tabs-as-spaces to just tabs
Merge pull request #171 from FMXpress/master

Fixed bug that left a '-1' tabindex on a select after destroying selectize