This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 115341 - [WorkbenchParts][PresentationAPI] Calling popup menu for editor or view tab should not activate it.
Summary: [WorkbenchParts][PresentationAPI] Calling popup menu for editor or view tab s...
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 4.4 M7   Edit
Assignee: Paul Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-07 11:56 EST by Eugene Kuleshov CLA
Modified: 2014-05-02 04:47 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2005-11-07 11:56:25 EST
Currently if you wan't to call editor or view popup menu (right-click on the
tab) this tab will be automatically activated, which means loading, initializing
or refreshing all the editor or view data structures. There are many cases when
such initialization is not really wanted by the usser (e.g. when he is trying to
close view or editor or change it to the fast view).

BTW popup menu on tabs in FireFox web browser does not activate tabls and that
works really nice.
Comment 1 Kim Horne CLA 2005-11-07 12:42:28 EST
Not sure if this would be fixed at the part or presentation level...
Comment 2 Paul Webster CLA 2006-09-28 15:17:10 EDT
Is this still a problem in 3.3?

PW
Comment 3 Eugene Kuleshov CLA 2006-09-28 15:23:09 EDT
Yes it is. Both editors and views are activated when you right-click on their tabs in order to open popup menu.
Comment 4 Paul Webster CLA 2007-06-21 13:30:12 EDT
See bug 112640 as well
Comment 5 Lars Vogel CLA 2014-05-02 04:47:55 EDT
The PresentationAPI has been deprecated with the Eclipse 4.x release and it has been replaced with the CSS engine. I therefore close this bugs as WONTFIX. In case your bug report is still valid for the Eclipse 4.4 release, please open a new bug report for it.