Bug 179048 - [Edit] doubleclicking added file in jar-zip comparison expands next folder
Summary: [Edit] doubleclicking added file in jar-zip comparison expands next folder
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 193321
Blocks:
  Show dependency tree
 
Reported: 2007-03-23 11:36 EDT by Markus Keller CLA
Modified: 2019-09-06 16:10 EDT (History)
0 users

See Also:

Attachments
one.jar (317 bytes, application/octet-stream)
2007-03-23 11:37 EDT, Markus Keller CLA 		no flags Details
two.zip (178 bytes, image/zip)
2007-03-23 11:37 EDT, Markus Keller CLA 		no flags Details
View All 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 Markus Keller CLA 2007-03-23 11:36:38 EDT 
I20070322-1800

Put the two archives I'll attach into an Eclipse project, select both, and choose Compare With > Each Other.

In the editor, doubleclick only-one.txt

=> zFolder is expanded, should stay collapsed
Comment 1 Markus Keller CLA 2007-03-23 11:37:19 EDT 
Created attachment 61836 [details]
one.jar
Comment 2 Markus Keller CLA 2007-03-23 11:37:43 EDT 
Created attachment 61837 [details]
two.zip
Comment 3 Michael Valenta CLA 2007-05-02 16:11:07 EDT 
I didn't get time to address this so I'll need to defer it. We're hoping to do work on Compare with Each other in 3.4.
Comment 4 Szymon Brandys CLA 2008-05-09 04:23:24 EDT 
Mass update - removing 3.4 target. This was one of the bugs marked for
investigation (and potential fixing) in 3.4 but we ran out of time. Please ping
on the bug if fixing it would be really important for 3.4, and does not require
API changes or feature work.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:10:10 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.