Difference between revisions of "Talk:Development:Planning:Shift Toggle"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
*Clicking a tab group since the first tab should always be focused. | *Clicking a tab group since the first tab should always be focused. | ||
*Double-clicking the tab bar to create a new tab. Nobody could think of a reason you'd want to open a new tab without having it in the foreground. | *Double-clicking the tab bar to create a new tab. Nobody could think of a reason you'd want to open a new tab without having it in the foreground. | ||
| + | |||
| + | ===Drags to the Content Area=== | ||
| + | These drags to the content area should always load in the current tab. | ||
| + | * 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 | ||
Revision as of 20:45, 26 May 2006
Actions that have been discussed and should NOT respect the pref/toggle
- Clicking a tab group since the first tab should always be focused.
- Double-clicking the tab bar to create a new tab. Nobody could think of a reason you'd want to open a new tab without having it in the foreground.
Drags to the Content Area
These drags to the content area should always load in the current tab.
- 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
