Development:Planning:Shift Toggle

From Camino Wiki
Revision as of 15:10, 26 May 2006 by Clawson (talk | contribs) (→‎Dragging to the tab bar: should respect pref and shift)
Jump to navigation Jump to search

Camino has a "load in background" pref to control whether new tabs/windows spawned in various ways load in the backgroud or foreground. In addition, the shift key acts as a toggle, causing the tabs/windows to be opened in the opposite state from the pref.

Actions that need to respect the background pref and shift toggle

Menus

  • Selecting a Bookmarks menu item (when cmd is held down, to open in new foo)
    • pref: Yes
    • toggle: Yes
  • Selecting "Open in Tabs" in the Bookmarks menu (only when cmd is held down)
  • Selecting a Bookmark Bar folder menu item (when cmd is held down, to open in new foo)
  • Selecting "Open in Tabs" in Bookmark Bar folder menus (only when cmd is held down)

Context Menu

  • Open Link in New Window/New Tab in the context menu
  • View image (when cmd is held down) in the context menu
  • Search (when cmd is held down) in the context menu
  • items in the Bookmarks Manager context menu/action button menu??

Text Entry

  • Cmd-return in location bar
  • Cmd-return in search bar

Toolbar

  • Cmd-clicking (and just clicking??) a tab group
  • Cmd-clicking a Bookmark Bar item
  • Any main toolbar buttons??

Dragging to the tab bar

Anything dragged to the blank area of the tab bar should open new tabs, respecting both the pref and the shift key.

  • Dragging a tab group to the tab bar
  • Dragging a bookmark folder to the tab bar
  • Dragging a Bookmark Bar item to the tab bar
  • Dragging a link on a page to the tab bar
  • Dragging a plain-text link to the tab bar
  • Dragging URL text from the location bar to the tab bar
  • Dragging a favicon from a tab or the location bar to the tab bar
  • Dragging one *loc to the tab bar
  • Dragging multiple *locs to the tab bar

Dragging to an existing tab

We need foreground/background distinctions here. Dragging to the current tab should have the same behaviour as dragging to the content area; dragging to a background tab is what we need to worry about.

  • Dragging a tab group to an existing tab
  • Dragging a bookmark folder to an existing tab
  • Dragging a Bookmark Bar item to an existing tab
  • Dragging a link on a page to an existing tab
  • Dragging a plain-text link to an existing tab
  • Dragging URL text from the location bar to an existing tab
  • Dragging a favicon from a tab or the location bar to an existing tab
  • Dragging one *loc to an existing tab
  • Dragging multiple *locs to an existing tab

Dragging to the content area

  • Dragging a tab group to the content area
  • Dragging a bookmark folder to the content area
  • Dragging multiple *locs to the content area

IMO, the behaviour of the above three is all we need to worry about. If you drag a single item of any sort to the content area, it should load in the current tab, period. Anything else doesn't make much sense.

  • Dragging a Bookmark Bar item to the content area
  • Dragging a link on a page to the content area
  • Dragging a plain-text link to the content area
  • Dragging URL text from the location bar to the content area
  • Dragging a favicon from a tab or the location bar to the content area
  • Dragging one *loc to the content area

To Do

  1. Seek reviews to see if any actions are missing
  2. Determine if any do not make sense on this list, if any
  3. Determine
    • which of these work
    • which of these do not, but are covered by existing bugs (and link to bugs)
    • which need to be filed (then link, once filed)