Closed Bug 184852 Opened 22 years ago Closed 22 years ago

Font resizing causes scroll bars to disapper

Categories

(Firefox :: General, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 185571

People

(Reporter: im4hiswork, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5

A few problems here....
1) Resizing font to above normal operations (as in huge fonts) on the page makes
the scroll bars disappear. The outline is there, the scrolling is operational,
but the scroll arrows are no long visible and the entire scroll bar is one
color. (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5)

2) Same problem in Windows 2000 as above (Mozilla/5.0 (Windows; U; Windows NT
5.0; en-US;rv1.3a) Gecko/20021207 Phoenix/0.5))

3)Decreasing size in same build of Phoenix for Windows 2000 will loop back to a
bigger font. Holding the cntrl+- buttons will loop back, it seems until orginal
font has been reached again.



Reproducible: Always

Steps to Reproduce:
Linux
1. Increase font (cntrl +)
2. Hold or keep hitting it, scroll bars go flush

Windows (Bug 2)
1. Same as above

Windows (Bug 3)
1. Decrease font (ctrl -)
2. Hold or hit multiple times until font is really small.
3. Keep hitting until the font rolls over (h# tags will go large first then on
the next hit the text goes)



Expected Results:  
Keep scroll bars normal (Bug 1 & 2)
Stop at small font (Bug 3)

Default theme in Windows. Pinball theme in Linux
Changing OS to "All" as more than one OS is involved...

Next I tried to dupe the problem, but it seems, that at least for the problem
making the scroll-bar flushing there are some more steps necessary (not only
hitting <ctrl><+> until end is reached, but going back to original size and
again increasing font-size)

Finally I encountered an additional problem with the comboboxes when trying to
dupe "bug 3", which is not mentioned here.

So from my point of view "bug 1" & "bug 2" needs to be described more detailed
as _one_ bug and "bug 3" should be described in a seperate bug.

I will try to get a more detailed description of these two cases, open seperate
bugs for them and resolve this one as "duplicate" to ease things for developers...
OS: Linux → All
I finally opened bug #185571 and bug #185573 for the described problems - hence
I will mark this one as resolved / duplicate of #185571 as no other resolution
fits...

*** This bug has been marked as a duplicate of 185571 ***
Severity: major → normal
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Mass verifying of old bugs.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.