Closed
Bug 271377
Opened 20 years ago
Closed 17 years ago
Minimum font size not respected when Ctrl + rolling mousewheel: font size becomes none
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: breght, Unassigned)
References
()
Details
(Keywords: helpwanted)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 All text disappears when using ctrl-scroll wheel to increase font size to really large and then back to smallest (form controls/images remain). I have tried this on different sites (with and without frames). The same behaviour is exhibited on www.google.nl, www.tweakers.net, www.mozilla.org etc.. A site with frames (www.webwereld.nl) didn't seem to have this problem, although I haven't thoroughly tested. The fonts I use are Bitstream Vera Sans, default set to 14, minimum to 9. This bug is *always* reproducible for these sites. Reproducible: Always Steps to Reproduce: 1. Navigate to site (e.g. www.google.nl) 2. (on PC/Linux) hold down CTRL-key while scrolling down with the mouse wheel to increase text size. Take a fair amount of `scrollings' so that the text becomes really large. 3. Now use the mouse wheel (still holding the CTRL-key) to scroll up, thus reducing font size until finally the text disappears. Images and form controls still remain on the page. Actual Results: All text (including hyperlinks) disappeared from the page Expected Results: Minimum font size should be respected (set to 9pt) Using Fedora Core 2
Comment 1•20 years ago
|
||
Confirmed. But it seems extremely trival to me. Should probably be moved to Core->Layout: Fonts and Text
Comment 2•20 years ago
|
||
Yes, the text disappears (font size becomes none); it will reappear if you roll the mousewheel (while holding down the CTRL-key) to increase font size again. As you say, minimum font size is not respected. Firefox 1.0 final release build 20041107 under XP Pro SP2 here. I could not find a duplicate for this. CONFIRMING because Minimum font size in Tools/Options.../Fonts & Colors is not respected. OS-> All
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Comment 3•20 years ago
|
||
I reedited the summary; an user Ctrl+ rolling the mousewheel can "reach" font size value "none". Product-> Core
Component: General → Layout: Fonts and Text
Product: Firefox → Core
Summary: All text disappears when using ctrl-scroll wheel to increase font size to really large and then back to smallest (form controls/images remain) → Minimum font size not respected when Ctrl + rolling mousewheel: font size becomes none
Version: unspecified → Trunk
Updated•20 years ago
|
Assignee: firefox → nobody
Keywords: helpwanted
QA Contact: firefox.general → core.layout.fonts-and-text
Comment 4•19 years ago
|
||
*** Bug 330415 has been marked as a duplicate of this bug. ***
| Reporter | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•17 years ago
|
||
This bug seems to no longer occur.
Comment 6•17 years ago
|
||
Breght, Resolving as FIXED is done only when we know which patch fixed the issue, otherwise we should just resolve as WORKSFORME. "Resolve a bug as FIXED if the bug has been fixed by a checkin into the Mozilla CVS code repository. Bugs which can no longer be reproduced should be marked WORKSFORME instead of FIXED if they can't be linked to a single checkin." What to do and what not to do in Bugzilla Resolving as FIXED http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html#resolving Also, when you say "This bug seems to no longer occur.", it is always preferable to add and to indicate explicitly which build version, revision version, on trunk or branch, which software (Seamonkey 1.x, Seamonkey 2.x, Firefox 2, Firefox 3?) in which it was noticed to be fixed. This helps in all kinds of ways users, QA people and the general maintenance of bug reports.
You need to log in
before you can comment on or make changes to this bug.
Description
•