Addressing issue #49 and fixing uppercase input value update during color pickup #57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e class added more examples in api sections in index html
…t and put swatch inside it
claviska
added a commit
that referenced
this pull request
Jan 20, 2013
Addressing issue #49 and fixing uppercase input value update during color pickup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moved input styling into minicolors-default-theme class to give option for developer to leave input styles unchanged by picker (please see #49 issue comment for more elaboration).
Fixed input value update during color pickup sliding to take into accounting case setting.
Added more examples to index.html to demonstrate/test how various configuration options behave.