Bug 418303 - No correct selection after "Open Specification"
Summary: No correct selection after "Open Specification"
Status: CLOSED FIXED
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P2 blocker (vote)
Target Milestone: 2.3   Edit
Assignee: Marvin Mueller CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-09-30 04:55 EDT by Sebastian Struckmann CLA
Modified: 2014-01-17 07:36 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Struckmann CLA 2013-09-30 04:55:41 EDT
After opening a test case or a test suite via "Open Specification" the context menu of the selected element in the first line of the editor is incorrect (It is e.g. still possible to choose "Delete") and the properties view is empty. Selecting a different element and then clicking back results in a correct context menu, where "Delete" is disabled, and a correct properties view.
It seems like the selection after "Open Specification" is still the same as the one before.
Comment 1 Achim Loerke CLA 2013-09-30 07:51:38 EDT
added SR2 target
Comment 2 Alexandra Schladebeck CLA 2013-11-25 06:15:27 EST
This is particularly evil in some circumstances:
- If an editor is already open, and the root node selected, then F3 / double click for open specification just brings the editor to the front.
- At this point, it looks like you can edit the properties. The editor becomes dirty after changes, and you can save. However, sometimes (I can't figure out according to which criteria), the changes are not actually made. After a refresh, they are gone. 

This feels very similar to a bug we fixed a while back that saving an editor led to a properties view being shown that could be edited and saved, but wasn't the correct properties view. 

The workaround is always to manually select the node you want to edit before making changes in the properties view, but that's not pretty.
Comment 3 Marvin Mueller CLA 2014-01-16 04:31:44 EST
I added the activation of the editor and also select the node via editor. The properties should now work correct.


Fixed with changeset: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=b5c4622c25d0819ac05b01a3f0afe23ef666fade
Comment 4 Markus Tiede CLA 2014-01-17 07:36:09 EST
I am no longer able to reproduce this issue.