Changed the implementation of CSS3 buttons to behave and look a little nicer with :active gradient reversal effect.
Simplified CSS, fixed font-family's and used em's for font-size properties.
Removed unneeded <script> tags.
Added a 2nd Default profile called "Alphanumeric", needed to update the test suite assertions to match for having 2 default profiles instead of just one.
Changed from using a Settings.getProfiles() function to simply accessing the Settings.profiles object directly
Changed to using addClass and removeClass instead of using .css/options.css() to directly alter CSS visibility property which is ~4-5x more efficient.
Added a nice big profile reset button to the General Options page to let users reset configured profiles.
General code cleanup, refactored out the custom character set click handler into its own function.
Fixed sync behavior by setting the Settings.syncDataAvailable variable at a decent time.
Removed getVerificationCode() off the Profile.prototype chain
Addresses issue #125
Added a delayedUpdate() function to be called on user input in the pop up to mitigate a possible visual replay attack that monitors result values.
Removes the little blue outline that appears around a button when clicked.
Added a .section class to options.html to reference the primary sections as 1 selector vs a big list of ID's which also simplifies the showSection() function.
Fixed a bug where there the getAutoProfileIdForUrl() function can't match a URL in the siteList if a siteList string entry includes + or ? characters, aka https://www.google.ca/search?q=space+test
Make sure password value is correct for both filling password fields and copying to the clipboard if wanting to use the resulting values in less than 600ms after adding a delay to prevent replay attacks.
Merge branch 'master' of https://github.com/bitboxer/chrome-passwordmaker into 6-update5
Also used a slightly better regexp since the 2x / were extraneous in group 1 since it's a negated character class not, negated literals, this DOES NOT change the resulting match.
Also made the 1st regexp group be a lazy match instead of a greedy match.
From agreement in PR #126 for not including the # fragment component of a URL, made it clear in the options page.
Some cleanup to CSS and chrome.tabs.query() tweaks for use in Opera, it bugs out and returns undefined when using currentWindow: true.
Changed repo URL in manifest.json to reflect joining github organization.
Use PBKDF2 to derive hashes/key to verify in 2 cases/places.
1) when saving the master password hash in options for password verification
2) the key used for syncing data instead of using the custom hash function which ChromePasswordMaker_SecureHash.make_hash() function provided in securehash.js.
Fixed some sync behavior while making sure to also sync the derived hash(salt) since we need the salt used to derive the hash on any synced computers.
Removed the ability to select the bugged md5_v6, hmac-md5_v6 and hmac-sha256 hash algorithms for new profiles.  They still work on import etc. but prevent the ability to choose them for new profile creation to encourage use of new, correct and secure algorithms instead.
The exact algorithm string can still be entered manually during profile import if needed.
Merge pull request #126 from heavensrevenge/6-update5

6-update5