Bug 125237 - [Contributions] Should MB_ADDITIONS be required?
Summary: [Contributions] Should MB_ADDITIONS be required?
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 144922 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-01-25 15:14 EST by David Dubrow CLA
Modified: 2019-09-06 16:17 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Dubrow CLA 2006-01-25 15:14:05 EST 
For tighter control over how our context menus look in various workbench parts we are creating, I tried not adding IWorkbenchActionConstants.MB_ADDITIONS to my popup menu contribution manager. However, PopupMenuExtender seems to require it, and otherwise logs its absence to the console, and then adds the contributions in any case. 

Would it be possible to allow workbench parts to refuse some contributions based on their target location? It seems natural that if MB_ADDITIONS is not added by the workbench part, those contributions targetted to that location should not be added.
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:56:37 EDT 
Moving Dougs bugs
Comment 2 Paul Webster CLA 2007-04-05 19:04:55 EDT 
Assigning to component owner
PW
Comment 3 Paul Webster CLA 2007-06-22 07:07:09 EDT 
*** Bug 144922 has been marked as a duplicate of this bug. ***
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:17:09 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.