Bug 272464 - [Apply Patch] Scrollbars missing after maximazing patch preview section
Summary: [Apply Patch] Scrollbars missing after maximazing patch preview section
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 05:13 EDT by Tomasz Zarna CLA
Modified: 2019-09-06 15:31 EDT (History)
0 users

See Also:

Attachments
Step 2 (64.51 KB, image/png)
2009-04-16 05:19 EDT, Tomasz Zarna CLA 		no flags Details
Step 3 (51.86 KB, image/png)
2009-04-16 05:20 EDT, Tomasz Zarna CLA 		no flags Details
Step 4 (63.74 KB, image/png)
2009-04-16 05:21 EDT, Tomasz Zarna 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 Tomasz Zarna CLA 2009-04-16 05:13:12 EDT 
N20090407-2000

Steps:
1. Open Apply Patch wizard
2. Preview a file to patch, pick a file that needs scrollbar to browse
3. Double click on the horizontal toolbar in the middle to maximize the bottom part of the preview
=> When maximized the scrollbar should be gone if the file fully fits current viewport 

4. Double click on the toolbar again to restore to normal size
=> The scrollbar should reappear, but it's gone so you cannot see the bottom part of the file

Screenshots illustrating the issue will follow
Comment 1 Tomasz Zarna CLA 2009-04-16 05:19:59 EDT 
Created attachment 132054 [details]
Step 2
Comment 2 Tomasz Zarna CLA 2009-04-16 05:20:36 EDT 
Created attachment 132055 [details]
Step 3
Comment 3 Tomasz Zarna CLA 2009-04-16 05:21:08 EDT 
Created attachment 132056 [details]
Step 4
Comment 4 Tomasz Zarna CLA 2009-04-16 05:22:37 EDT 
Workaround: resizing the dialog manually forces the scrollbar to show/hide.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:31:00 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.