Closed
Bug 128542
Opened 23 years ago
Closed 22 years ago
Lines in outliner are too narrow, some characters at cut off at the bottom (e.g. cookie manager dialog).
Categories
(Core :: XUL, defect, P3)
Tracking
()
mozilla1.0
People
(Reporter: andre.bugs2, Assigned: janv)
Details
(Keywords: qawanted)
Attachments
(6 files)
[Build-ID: 2002-03-01-16] I've seen this for ages, but I have never seen it reported. Sorry if it is a dupe. A screenshot best describes this bug, so below I will attach a screenshot of this bug. In the cookie manager the lines seam to lie too close to eachother, and characters with "tails" (such as 'g') often loose the bottom most part of itself. The line below it overlaps it, in other words. Notice that it only seams to happen on entries high up in the list of cookies, which is weird. I think if first saw this bug after the cookie viewer had been converted to Outliner, but I am not 100% on that. I wouldn't be surprised if this is Linux-only.
Reporter | ||
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
->Cookies/future
Assignee: trudelle → morse
Component: XP Apps → Cookies
QA Contact: sairuh → tever
Target Milestone: --- → Future
Comment 3•23 years ago
|
||
Although this shows up in the cookie dialog, it's nothing unique to cookies but must be a general problem with outlines. Reassigning.
Assignee: morse → hyatt
Component: Cookies → XP Toolkit/Widgets: XUL
QA Contact: tever → jrgm
Reporter | ||
Comment 4•23 years ago
|
||
Yes, I agree. I think I have seen the same thing happen in the newsgroups view.
Comment 5•23 years ago
|
||
Changing summary to reflect that this is a general problem and not a cookie viewer one.
Summary: Lines in cookie viewer are too narrow, some characters at cut off at the bottom. → Lines in outliner are too narrow, some characters at cut off at the bottom (e.g. cookie manager dialog).
Comment 6•23 years ago
|
||
bryner, can you take a quick look? Cc'ing hyatt, varga, and trudelle. /be
Assignee: hyatt → bryner
Reporter | ||
Comment 8•23 years ago
|
||
Jan, that bug certainly sounds similar. I don't like the fact that it's still in the Mail/News category, and doesn't have a screenshot, but feel free to dupe this one if you feel it has more info than this bug.
Comment 9•23 years ago
|
||
If this is a general problem, then we need steps to reproduce. ->qawanted. JRGM, could you look into this and nominate as appropriate? Jan, could you take this if needed, since bryner is in form control hell?
Keywords: qawanted
Comment 10•23 years ago
|
||
FWIW, I'm not seeing this on windows. The interline spacing that I am seeing is much greater than the one in the posted screenshot. So maybe it is a linux-only problem.
Assignee | ||
Comment 11•23 years ago
|
||
I guess, it's font problem. Taking for now.
Assignee: bryner → varga
Reporter | ||
Comment 12•23 years ago
|
||
Jan, what info is valuable for you? Here is some info on my system: I'm running Debian GNU/Linux unstable with XFree86 4.1.0. This bug happens with a clean profile, so in other words no font settings have been changed in mozilla. My font server (xfs) serves fonts with 100dpi. Below I will attach the output of 'xdpyinfo' in case it is helpful.
Reporter | ||
Comment 13•23 years ago
|
||
Comment 14•23 years ago
|
||
-- foo.css -- to go with attached test case; vary font-size until you get descenders to overlap with text below. outlinerchildren { font-family: sans-serif; font-size: 16pt; }
Comment 15•23 years ago
|
||
So, yeah, as you increase the font-size for the text in the outliner, at about 14pt/sans-serif on windows, and about 18pt/serif on linux (for the machines and fonts that I tried), there is some problem with descenders from the line above overlapping with text in the line below. (Sidenote: I don't really understand what the screenshot is supposed to show; all the rows are blank). It seems that the rows are either not measuring the text correctly, or are capped to a max-height and don't grow with the text. In general, this isn't an issue, but it could be an issue for visually impaired who are using large fonts to compensate.
Assignee | ||
Comment 16•23 years ago
|
||
Thanks for info. This is the same problem as in 73984. And it sounds reasonable to me. An outliner uses fixed height (currently 18px) for performance reasons outlinerchildren:-moz-outliner-row { border: 1px solid transparent; height: 18px; } It would be a big overhead to adjust height to real text height. Still looking for a way to solve this problem w/o perf impact.
Assignee | ||
Comment 17•23 years ago
|
||
jrgm, there is a problem with the screenshot (png problem I guess) I see blank rows too, but only in ns4x
Status: NEW → ASSIGNED
Reporter | ||
Comment 18•23 years ago
|
||
The thing is that I have not set my fonts any larger than the standard value.
Assignee | ||
Comment 19•23 years ago
|
||
The standard value may be not well tuned too. Anyway, I've got an idea to fix this bug, working on a patch...
Assignee | ||
Comment 20•23 years ago
|
||
it seems that fix is very easy - height: 18px; + height: 1.5em; :)
OS: Linux → All
Priority: -- → P3
Target Milestone: Future → mozilla1.0
Comment 21•23 years ago
|
||
doh :-). Yes, that CSS thing is kind of cool.
Assignee | ||
Comment 22•23 years ago
|
||
Comment 23•23 years ago
|
||
Although, is it certain that when using 'em' for the max-height, that the row height for the entire outliner will only be calculated once?
Reporter | ||
Comment 24•23 years ago
|
||
I applied the patch from attachment 72957 [details] [diff] [review] on a CVS tree from the 0.9.9 branch, and this is how it looks. The distance between the rows are not instead too big. At least IMHO:-)
Assignee | ||
Comment 25•23 years ago
|
||
I think you have bigger font in general
Assignee | ||
Comment 26•23 years ago
|
||
a good value for windows is 1.7em; Now I'm not sure again :(
Assignee | ||
Comment 27•22 years ago
|
||
*** This bug has been marked as a duplicate of 86532 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•