The default bug view has changed. See this FAQ.

Unwanted horizontal scrollbars on Google Reader

RESOLVED FIXED

Status

()

Core
Layout: Text
P2
normal
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: Sylvain Pasche, Unassigned)

Tracking

({regression})

Trunk
x86
All
regression
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9.2 +

Firefox Tracking Flags

(status1.9.2 beta1-fixed)

Details

(URL)

Attachments

(2 attachments)

(Reporter)

Description

8 years ago
Created attachment 388113 [details]
testcase, partly reduced

Appears to be a regression from bug 475968. Horizontal scrollbars are visible below the text on every feed item.

Attached testcase links to the Google CSS, it would certainly appreciate some more reduction.
Flags: blocking1.9.2?
(Reporter)

Comment 1

8 years ago
By the way, it happens with ClearType turned on or off.
It happens with or without ClearType turned on because the underlying issue exists even with "standard" antialiasing -- glyphs may paint pixels just beyond their nominal bounds -- the discussion generally centers on CT because that's when it becomes really noticeable. Without CT, the potential drawing problems (clipping, artifacts) are so minor that they're unlikely to be noticed and reported.

And the unwanted scrollbars appear on OS X as well, due to bug 476927 which was the Mac equivalent to the Windows ClearType issue.
Marked as "all" platforms although I assume it's really just Windows and Mac; we don't seem to have an option for selecting several separate choices.
OS: Windows XP → All
I think the right way to resolve this (and resolve or pre-empt other similar issues*) would be to stop overloading the concept of the frame's "overflow area". The trouble is that "visual overflow", needed for correct painting/invalidation, may be different from "structural overflow", which is what determines the appearance of scrollbars, and relates to the CSS overflow property.

Although it's conceptually simple, it means checking each place in layout where overflow is set, used, or propagated up the tree, to determine which kind(s) of overflow it should be considering. Roc, WDYT?

(*) Just as I was typing this comment, I saw a horizontal scrollbar appear momentarily at the bottom of the input area, as the cursor reached the right edge of one line. Probably a manifestation of the same problem.
You're right. I had Karl lined up to do that but he's been busy with other bugs.

Probably we should back out bug 475986 and bug 476927 until that's done.
Created attachment 388202 [details]
simplified test case

A simplified test case with three versions of a Google Reader-like <div>.

In testing on Mac OS X and Windows, Firefox 3.5 shows no scrollbar on the first example, but the second and third (using a larger font size, or setting the optimizeLegibility hint) have scrollbars.

Current Minefield trunk build shows scrollbars on all three versions of the <div>. The patches from bug 475986 and bug 476927 just make it likely that the unwanted scrollbar will appear in more circumstances, but the underlying problem was already present.

(BTW, Safari 4 does not show a scrollbar in any of these test cases. I think that's more correct.)
Duplicate of this bug: 503909
Blocks: 476927
Fixed by backouts.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
I think the references to bug 475986 above should all reference bug 475968 instead.
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
There is one one place where scrollbars still appear in Google Reader.

If you click on "People you follow" it places a scrollbar under their name when you click their link.  I don't know if this is worth reopening the bug, but I thought I would mention it before we Verify it as Fixed.
Mass change: adding fixed1.9.2 keyword

(This bug was identified as a mozilla1.9.2 blocker which was fixed before the mozilla-1.9.2 repository was branched (August 13th, 2009) as per this query: http://is.gd/2ydcb - if this bug is not actually fixed on mozilla1.9.2, please remove the keyword. Apologies for the bugspam)
Keywords: fixed1.9.2
status1.9.2: --- → beta1-fixed
Keywords: fixed1.9.2
You need to log in before you can comment on or make changes to this bug.