* Create a new tab in a group which has more than one tab. While in
tabcandy, close that tab. Now you're zoomed into the tab to its left.
You should instead remain in TabCandy.
* Another improvement for the command+e keyboard combination.
+ Create two groups; one with a single tab and another with several
tabs. Go into the single tab and then close the tab. You return to the
TabCandy interface as you should, but you see one of the other tabs
zooming out. There should be no zoom out in this case. [RAYMOND]
+ Cmd+e key combination is not working in the tab candy.
+ close buttons on tabs are still not showing correctly. Add a bunch
of tabs to the tabstrip so all close buttons for background tabs are
hidden, go into Tab Candy interface and remove tabs until you know the
close buttons should appear. Then, zoom into a tab and the close
buttons on back
+ Added "reset" to the dev menu so we can test first run (since the reset button is currently AWOL)
+ Added Utils.assertThrow(), an assert that throws an exception
+ Created a platform-specific css file for tabcandy in the theme directory.
+ Copied the Mac TabCandy theme additions into the Windows and Linux themes.
--HG--
rename : browser/themes/pinstripe/browser/tabcandy/tabcandy.css => browser/base/content/tabcandy/tabcandy.css
- moved Group._getBoundingBox to Groups.getBoundingBox; now a better algorithm which is order-independent.
- modified "drag tab onto another tab" action's phantom group computation using getBoundingBox: now a touch more realistic.
+ Item.snap, which is used to instantaneously resituate oneself into a more trench-inspired position, using wider radius trenches.
- Group constructor now runs Item.snap, so all new groups are marginally better positioned.
- correcting my foolish ways: replacing some tabs with spaces.
+ Removed TabItems.reconstitute(), which we haven't actually needed for a while, but now it's also causing trouble
+ Removed Utils.activeWindow, which doesn't seem to work, and replaced its use in Utils.activeTab (the only remaining place it was being used) with Utils.getCurrentWindow(), which does seem to work
+ Utils.assert() now dumps a trace
+ Fixed paths to the edit pencil and new tab button images; they should now show up properly
