Bug 696622 - Font resize GUI feature usability
Summary: Font resize GUI feature usability
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: cumin
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 2.1
: ---
Assignee: Trevor McKay
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-14 13:04 UTC by Jan Sarenik
Modified: 2011-08-31 12:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-18 16:00:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Sarenik 2011-04-14 13:04:57 UTC
If you resize font using [ S, M, L ] inside GUI tab, the setting is
not preserved when you change to other tab.

By the way, this functionality is included in the browser -
does it make sense to cope with it in Cumin at all?


cumin-0.1.4712-1.el5

How reproducible: 100%

Steps to Reproduce:
1. Click on a letter which changes font size in current tab.
2. Click on other tab.

Actual results: The font size in the other tab is reset to the original.
  When you return back to the tab you have changed the font size in,
  the size is restored, but just for that particular tab.

Expected results: Font size change should affect Cumin globally.

Additional info: Maybe it's not even needed (CTRL + wheel does the job)

Comment 1 Matthew Farrellee 2011-04-14 14:01:31 UTC
Re: By the way, this functionality is included in the browser - does it make sense to cope with it in Cumin at all?

Scaling in browsers will scale the entire page. The S,M,L scaling provided on Cumin tables applies only to the text within the table.

-

I'm not sure this is a bug. It would be reasonable to assume different tables have different amounts of/layouts for data, and changing table font sizes independently is a feature. It is similar to direct browser scaling, which in FF3 is sticky to where the scaling originally occurred.

Comment 3 Justin Ross 2011-04-14 20:03:14 UTC
I agree with matt about different tables requiring different "zoom".  It makes sense to me to preserve the user's preference on a per table basis.

(NB, I think this should be done by first adding support for persistent client sessions.)


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