Closed
Bug 233378
Opened 22 years ago
Closed 20 years ago
Home page (accueil link) appears without a scroll bar when it should have a scroll bar. This results in about half the content of the page not being displayed.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: hleclerc, Unassigned)
References
()
Details
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
The problem is on page at http://www.fpmsolutions.net/cgi-bin/home.pl
There are no scroll bars appearing when there should be.
Reproducible: Always
Steps to Reproduce:
1. go to http://www.fpmsolutions.net/cgi-bin/home.pl
2. scroll down to the bottom of the page with the mouse wheel (must have a
screen resolution of 1280x1024 or lower otherwise you will probably see the
whole page).
3. scroll back up to the top of the page.
Actual Results:
The page background becomes black when at the bottom of the page and when
scroll back up it is impossible to scroll down to the bottom of the page after.
Expected Results:
The software should display scroll bars since the content of the page is larger
than the size of the window browser.
Comment 1•22 years ago
|
||
All the content is in an absolutely positioned div inside a table. So the
<body> of the page is in fact quite a bit shorter than the viewport....
Is this a problem with tables not propagating overflow areas right?
Summary: Home page (accueil link) appears without a scroll bar when it should have a scroll bar. This results in about half the content of the page not being displayed. → Home page (accueil link) appears without a scroll bar when it should have a scroll bar. This results in about half the content of the page not being displayed.
| Reporter | ||
Comment 2•22 years ago
|
||
(In reply to comment #1)
> All the content is in an absolutely positioned div inside a table. So the
> <body> of the page is in fact quite a bit shorter than the viewport....
> Is this a problem with tables not propagating overflow areas right?
Could be. The problem could also come from the fact that the "security" part of
the page comes from symantec security response and is therefore added in the
page tree through javascript.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 5•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•