Here is some tweak to keep the UI coherent ![great border-radius](https://s3-eu-west-1.amazonaws.com/uploads-eu.hipchat.com/130388/947678/oMGsqH0h2eAE8dT/Capture%20d%E2%80%99%C3%A9cran%202015-02-26%20%C3%A0%2017.39.27.png)
…lease tonight (Feb 25, 2015) broke compatibility (a class-name changed).
… if the username contained parentheses.
…ase of Trello code today.
…ork. This change will ignore spaces.
…rello added an iframe, and our selector was catching it and attempting to work with it which resulted in permissions errors which broke the saving of settings on Chrome, and broke the entire extension on firefox.
…t submitted (v1.86 includes the fixes to Settings panel in Firefox).
… without impacting Chrome (and presumably without impacting Safari, but that hasn't been tested yet... no need to release this version on Chrome or Safari urgently).
…new version of Trello.
…new version of Trello (currently in Beta, rolled out to 1% of users) and to continue working for the current stable version. Everything that I thought to test appears to be working fine with this commit. Testing was only done in Chrome so far.
The settings control the visibility of the Burndown Chart link and what the estimate button numbers will be. By default,the settings are stored in chrome cloud storage (so that they're synced across browsers). If a browser does not support that, then they're stored in LocalStorage if possible. If LocalStorage isn't available, then the settings are stored in cookies.
… on the right by themselves. Vertically-centered the estimate/time-spent number totals in the bar up top. A great deal of groundwork for the Scrum for Trello settings. The settings aren't finished yet, so the icon itself is still hidden (commented out near line 188). Will attempt to finish the settings very soon. This commit includes icons that will be used by the settings link and the small window/frame it pops up.
…on to the same point as v1.5.2 in FF and Safari. This includes minor changes to make the code more cross-browser compatible, and to update the manifest. If this version passes our testing, it will be a candidate to be pushed to the Chrome app store.
…orted by github user "rdkls".
…were done to Master after that point. This includes the immediate update of points-badges after a card's estimates change. Additionally, this version has significant performance improvements over pull-request 55. CPU usage for the extension is now 0% on Chrome most of the time and only slightly higher in FF.