Bug 319481 - resizing doesn't work properly
Summary: resizing doesn't work properly
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 8
Hardware: All Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-05 00:02 UTC by Thorsten Scherf
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-05 13:57:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Thorsten Scherf 2007-10-05 00:02:59 UTC
Description of problem:
I'm using evolution from f8test3 and resizing on 1024x768 doesn't work properly. 

Version-Release number of selected component (if applicable):

How reproducible:
start evolution
try to find the scrollbar
try to make the window somehow smaller

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Matthew Barnes 2007-10-05 00:19:31 UTC
I'm not sure I understand...

> try to find the scrollbar

What scrollbar?

> try to make the window somehow smaller

Make sure the window is not maximized.  Grab the corner of the window and drag.

Comment 2 Thorsten Scherf 2007-10-05 09:07:47 UTC
ok, I try to be more precise:

When I maximize the windows, I expect to to see the scroll bat on the right side
of the message windows (classical layout is used) to scroll through the message,
this scrollbar is no accessable. the next problem with this view is, that I can
not resize the left part of the window where all of your folders are listed. it
simple does not resize when I move the mouse over the scrollbar there and drag
it a bit to the right side.

this all worked on my f7 box.

Comment 3 Thorsten Scherf 2007-10-05 13:57:54 UTC
hm, machine rebooting fixed that issue...


close this bug.

Note You need to log in before you can comment on or make changes to this bug.