OK, after opinions and debate, here’s what I’ve come up with.
I’ve combined the source view and the internal representation into one tabbed window so I only need one action to display it.
For now, that action will only be available when you are in microformats mode with all handlers displayed AND debug mode. When that is done, you will have a new menu in the handlers that says “Debug” that displays the information. I might add a keystroke/mouse action later.
When a microformat is invalid, clicking on it will display the same window (again, debug mode only)
I am going to honor the browser settings for Ctrl/Shift behavior for opening new windows. This however has me in a new quandry.
Here’s the note I sent to the Mozilla usability folk (Mike Beltzner):
I’m looking into making operator honor the browser preferences related to opening links (in tab, in tab background, in new window, etc.)
On investigating this problem, I found that there are two prefs that control this functionality;browser.tabs.loadBookmarksInBackground
browser.tabs.loadInBackground is used for content, and browser.tabs.loadBookmarksInBackground is used for chrome (I’m guessing mainly bookmarks)
The user can’t change browser.tabs.loadBookmarksInBackground easily – the pref UI only changes browser.tabs.loadInBackground.
So my question is, which preference should Operator use for opening links (what would a user expect)
Would they expect it to behave similar to content or similar to bookmarks (chrome)
Note the biggest difference here is what happens when Ctrl and Ctrl+Shift are pressed when opening a link.
Incidentally, by default these preferences are opposite which makes for a horrid user experience.
Create a new profile in Firefox 2.
Hold Ctrl key. Click on a link in content. Then hold Ctrl and click on Getting started in the toolbar – two different results. That sucks.
Thanks for your input.
More opinions welcome