So what can be done about it?
If I were to write a full extension, I’d scrap the whole ‘toolbar’ idea. Chrome supports very minimal UI options, but it does have some! First off, it has the notification buttons. If Chrome doesn’t limit you to only 1 button per extension, why not make the major stumble button and a separate button to have a menu for Share, Account, etc.
Since it looks like you can only have one browser_action (button) per extension, then try moving the “stumble” browser_action into the top of the stumble menu browser_action. Then launch a stumble button extension for power users that don’t like having to click+wait+click for random stumbling.
I only use the toolbar for the share button and drop down. I get email alerts whenever a friend shares with me, which combined with a GMail Notifier gives me a live view of my friends shares. I rarely (/never) use the Stumble button anymore since I’ve started browsing Reddit.
The StumbleUpon Share Bookmarklet
So ultimately, I wrote a bookmarklet to inject just the share box.
Creating the Bookmarklet
Creating the bookmarklet was fun. It is by all means not perfect probably, as I didn’t sweep through it for minimalism. Nor is setting a global object the best approach. I also found out that browsers (or just Chrome?) don’t let you get objects created in a top frame from an iframe unless the protocol and domain match. Thus I wasn’t able to hook the closing call after a successful share.
I also found out that dynamically created fixed objects will have it’s x coordinate relative to the #anchor tag if found. I relearned to always encode my URLs before submitting them as parameters.