need to add delete tab move up/down print tab stop
You see, Kevin? I told you this would happen. What's next after `Print Tab ...' and `Stop', I wonder? `Save As ...', perhaps? `Reload'? `Send Panel ...'? `Select All'? `Text Encoding'? `Use Style'?
Depends on: 66933
Hardware: PC → All
Summary: context menu's in sidebar → Context menus in sidebar
Actually, I'm the one asking for these as well. I understand your point, it's very well taken. What I want to ensure is that we look at these for their greatest utility for the average user. I would easily forgo the less common functions in favor of the convenience items we're discussing. FYI - we've got a couple of those you mention in there already. ;-)
Bah. Just fix bug 42758, and make menu items apply to the sidebar panel when it has focus. Then users will have *all* the utility and none of the clutter, and we won't have to take these silly items out again later.
Some of these items (remove panel/move up/move down) would have to show up when you right-click the top of the tab, because some types of sidebar content don't have context menus at all. Some of these items (stop, print) make more sense for when you right-click on the panel's content and the content happens to be HTML or something else that acts in a similar way.
Good point. Are these different behaviors possible?
Marking p3, nsbeta1+, mozilla0.9.1
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P3
Target Milestone: --- → mozilla0.9.1
We have most of the context showing up now. Need to add the ones that kevin wants.
as discussed in team meeting, moving all Nav+ team members nsbeta1+ P3 bugs from mozilla0.9.1 to mozilla0.9.2.
Target Milestone: mozilla0.9.1 → mozilla0.9.2
sidebar triage: moving to mozilla1.0.
Priority: P3 → P4
Target Milestone: mozilla0.9.2 → mozilla1.0
Revision of sidebar context menu items will be tracked by bug 41445. *** This bug has been marked as a duplicate of 41445 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.