Closed
Bug 174072
Opened 22 years ago
Closed 22 years ago
When I went to about:plugins the file names come up unreadable.
Categories
(Core Graveyard :: Plug-ins, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.4beta
People
(Reporter: wellander2, Assigned: kairo)
References
()
Details
(Whiteboard: [PL2:NA])
Attachments
(2 files)
23.09 KB,
image/png
|
Details | |
552 bytes,
patch
|
kairo
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2b) Gecko/20021011
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.2b) Gecko/20021011
Hi,
When I went to check what plugins I have configered for my browser I could not
read the c:\ file names they have lines thruogh them. Phoenix 0.2 alos has that
problem. I can not figer out why that is happening.
Reproducible: Always
Steps to Reproduce:
1.Type about:plugins in the url bar.
2.
3.
Actual Results:
The same.
Expected Results:
To let me see the file names.
Comment 1•22 years ago
|
||
*** Bug 174073 has been marked as a duplicate of this bug. ***
Comment 2•22 years ago
|
||
Can you please attach a screenshot ?
Comment 3•22 years ago
|
||
I can see this on build 2002101015, using Modern theme, too. Confirming, and
will attach screenshot.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•22 years ago
|
||
Seems to depend on the "message font", which is MS Sans Serif on my system.
Comment 5•22 years ago
|
||
beppe, u saw this last week , I remember.
Comment 6•22 years ago
|
||
In fact, I'm sure it's "message font" that causes this, because when I comment
out that line in plugins.css, it fixes the problem.
Comment 7•22 years ago
|
||
yes I saw this on win98 but I am not seeing it on winXP. Assigning to Anthony to
see if he can hunt down the root of the issue
Assignee: beppe → anthonyd
Priority: -- → P4
Whiteboard: [PL2:NA]
Target Milestone: --- → mozilla1.4beta
I can't reproduce this, and I groked my plugins.css for "message font" and
couldn't find it. I also tried playing with the fonts in the prefs panel and
could'nt get it to happen either.
Can anyone give me some clues?
Status: NEW → ASSIGNED
Comment 9•22 years ago
|
||
Only happens with certain themes. Modern seems to have this problem, but
Classic doesn't. I was working on a theme of my own and had this problem. I
believe the problem only happens if the font used for "message-font" is actually
a bitmap font instead of a TrueType font. That *should* mean you won't see it
on WinXP, and possibly not on Win2K, either, since I think all the default
system fonts are TrueType. That would imply it's Win9x, possibly NT4, only.
Comment 10•22 years ago
|
||
*** Bug 175566 has been marked as a duplicate of this bug. ***
Comment 11•22 years ago
|
||
I cannot reproduce this on win2k with the modern or classic theme. Does anyone
have the ability to test this on winNT?
Comment 12•22 years ago
|
||
I cannot repro this on winXP, but can dup it on win2K -- sorry I do not have NT
Comment 13•22 years ago
|
||
*** Bug 174138 has been marked as a duplicate of this bug. ***
Comment 14•22 years ago
|
||
*** Bug 180225 has been marked as a duplicate of this bug. ***
Comment 15•22 years ago
|
||
Could this be a result of users not having the specified font from the style
sheet? When I looked at chrome://communicator/skin/plugins.css it calls for the
lable to be italic, if I change that to normal, the text renders fine.
Robert: could you possibly revert the label to normal instead of italic?
Assignee: anthonyd → kairo
Status: ASSIGNED → NEW
Comment 16•22 years ago
|
||
Beppe, as I mention in comment #9, I'm pretty sure the problem is due to the use
of a bitmap font. Since bitmap fonts only have certain sizes, I would guess
your idea may be what's happening. I don't know how Mozilla internally handles
the case where the font returned by the system isn't *exactly* the same as the
one requested.
Comment 17•22 years ago
|
||
Right: it may be a combination of things -- it might be simpler to refer to
either serif or sans-serif and let the system pick an appropriate font in that
family. Removing the italic helped, could be that the replacement font for the
bitmap font did not have italic (a guess anyway).
Robert: any chance of possibly using a family rather than a specific font and style?
Assignee | ||
Comment 18•22 years ago
|
||
beppe:
Well, it's no problem to use family, I just thought it should blend in with the
theme's other choices of fonts, and re-used that.
I think it may be better to just remove italic and continue to use the same font
as those themes use for other UI elements as well. It seems we don't use italic
in UI anywhere, I never realized that :)
Comment 19•22 years ago
|
||
sure, that sounds fair
Assignee | ||
Comment 20•22 years ago
|
||
This patch removes that italic definition from the mordern theme, as it seems
we don't use italic anywhere else in UI, this also helps consistency.
Comment 21•22 years ago
|
||
r=beppe
looks good
Assignee | ||
Comment 22•22 years ago
|
||
Comment on attachment 106813 [details] [diff] [review]
patch: removing italic definition
adding r=beppe, requesting sr= from bz
Attachment #106813 -
Flags: superreview?(bzbarsky)
Attachment #106813 -
Flags: review+
Assignee | ||
Comment 23•22 years ago
|
||
hmm, the new attachment flag system lists it as if I would have given r= - would
be better if beppe would have set review+ on the attachment himself...
Updated•22 years ago
|
Attachment #106813 -
Flags: superreview?(bzbarsky) → superreview+
Assignee | ||
Comment 24•22 years ago
|
||
Checking in plugins.css;
/cvsroot/mozilla/themes/modern/communicator/plugins.css,v <-- plugins.css
new revision: 1.2; previous revision: 1.1
done
fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 25•22 years ago
|
||
*** Bug 183794 has been marked as a duplicate of this bug. ***
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•