Open
Conversation
Generate all possible upper- and lowercase mixes. Update .noConflict to match. Reset whitespace.
Remove the last use of forEach.
Following the original look.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes the last open issue #3 in a way I think is satisfactory to most: every combination of lower- and uppercase characters can now be used.
More code than I originally planned but I did not want to forego support for IE8 by using array manipulations such as
mapandforEach. (Getting mixed-case strings usingmap.)Additional changes:
use strict)/*jslint browser: true, plusplus: true, indent: 2 */.After nearly 3 years, @mathiasbynens will finally be able to use
qUeweRy.