Closed Bug 312505 Opened 19 years ago Closed 18 years ago

Horizontal scrollbar is out of reach until you scrolled to the very bottom

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: ZookQValem, Unassigned)

References

(
URL
)

Details

(Keywords: regression, testcase)

Attachments

(1 file)

testcase
581 bytes, text/html
Details 
When a web page is rendered, the horizontal scroller is out of reach making it
impossible to scroll sideway (right/left motion).  But when you scroll
vertically all the way to the bottom, the horizontal scroller is visible. 
Problem is you'll have to slide the horizontal scroller to the right a little
then you'll have to use the vertical scroller to scroll all the way to the top
to read the article.  Jumping back and forth vertically and horizontally is not
a healthy way to read the web page.

Bug visible in Seamonkey build #2005101005 and Firefox build "Deer Park Alpha
2", both of them from the nightly build a few days ago.
Component: General → Layout
Product: Mozilla Application Suite → Core
Version: unspecified → Trunk
Behavior changed sometime between 2004-09-01 and 2004-10-01.
Keywords: regression
OS: Windows XP → All
Hardware: PC → All
Attached file testcase — 
The combination of "overflow-x: auto" on the <html> and "overflow: auto" on the
<body> is causing the scrollbar to appear at the bottom of the content rather
than at the botom of the viewport.
Note that Gecko 1.7 did not support "overflow-x", which is probably why this
not happen there.

Notice this comment in the original css file:
html{
	overflow-x: auto; /* fixes MSIE scrollbar bug DO NOT REMOVE, has no
effect in Mozilla, or Opera */
}
Keywords: testcase
Keywords: regression, testcase
OS: All → Windows XP
Hardware: All → PC
OS: Windows XP → All
Hardware: PC → All
Keywords: regression, testcase
*** Bug 312584 has been marked as a duplicate of this bug. ***
Summary: Horizontal scroller is out of reach until you scrolled to the very bottom → Horizontal scrollbar is out of reach until you scrolled to the very bottom
I'm tempted to mark this INVALID. What happens here is that the overflow-x on
the HTML element is propagated to the viewport. Then, because 'overflow' on the
HTML element is not 'visible', we do not propagate the BODY 'overflow' style to
the viewport, so BODY ends up 'overflow:auto'. That produces the effect that you
see here, and IMHO it's quite reasonable and correct.
On this page...no scollbar appears at all.
This is totally broken
http://www.discoverysoftware.co.uk/forums/index.php?showtopic=5&st=0&#entry92
Works for me, on trunk. What makes you think it's the same bug, anyway?
(In reply to comment #6)
> Works for me, on trunk. What makes you think it's the same bug, anyway?

It doesn't WFM in a 2005-10-15 trunk build (there's no horizontal scrollbar,
although the bottom message does overflow).

It does seem to be related, as the style contains:

html { overflow-x: hidden; overflow-y: auto; }

with the obligatory /* FIX IE6 Scrollbars bug - Leave this in! */ comment.
This is another case where we're doing exactly what the page asks us to do. What
is the problem?
Not sure if that last question was directed at me, but anyway: while I
understand that this bug is technically invalid (it wasn't me who confirmed it),
it seems that these pages do not currently behave the way their designers had in
mind (apparently they were trying to work around some IE bug, counting on the
fact that Gecko doesn't understand overflow-x).

I don't know if this a severe or widespread enough problem to justify a quirk
(if such a quirk is possible), but I suspect it isn't.
I realize that the official position is to blame the websites.
That is why I  have turned my back on the seamonkey project.

Because, it is the height of stupidity to take such a position. Not to
mention arrogance. Let's get this straight...whatever the reason, this
bug renders seamonkey TOTALLY USELESS.

This problem does not, I repeat NOT occur with any other browser.
Thus, blaming it on the page is beyond moronic(even if technically true.)

Mozilla, IE, Firefox, Opera ALL HANDLE IT CORRECTLY.
Seamonkey, does not.

What a joke.
> I understand that this bug is technically invalid (it wasn't me who 
> confirmed it),...
Well, there was no unconfirm or confirm when I filed this bug, it was automatically as new.  Must be a new bugzilla feature or something.  

Anyway, I was hoping to have time to research this bug some more but I didn't.  After reading your comment and I would agree but I think more research is needed to find out what had changed between those dates that cause this issue to be able to determine if this is a bug or not.  Then compare it to the w3.org documentation.  Then we'll know for sure.  Make it easier for somebody to resolve a duplicate bug to this one.
Yeah, this is invalid.  What's changed is that we added support for "overflow-x" per the CSS3 proposal.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: