Not sure if this is a layout or necko problem, but if I go to www.theonion.com, and click on the full text link (about the senate candidate who drops out because of shyness), the page doesn't layout completely, and there are no scroll bars, though not all the page is displayed. If I go directly to the page in question, it does lay out fully. This problem only happens, it seems, when I click on the link that takes me to that page. The other funny thing is that Back does nothing the first time when I'm on this page, and if I hit it again, it skips the previous page and goes back to my browser start page.
I think something's going on in the networking code. The page doesn't even want to load for me with today's build
Assignee: troy → gagan
Component: Layout → Networking
QA Contact: petersen → tever
Assignee: gagan → rpotts
Target Milestone: M14
Nope... I think that layout is in charge of scrollbars :-)
Assignee: rpotts → troy
What does this have to do with scrollbars? It was bug 29229 that you claimed had something to do with scrollbars
Assignee: troy → rpotts
What I'm seeing is that the document loads, but no scrollbars are created :-( You can see a little more of the document by resizing the window, but you *never* get any scrollbars :-( Networking? I think not :-)
this has been happening for quite a while - I'm glad someone else can reproduce it!
Well, with today's tip build, I'm seeing the page load fine and the scrollbars appear - as expected... It looks like yesterday's tip exhibited the scrollbar bug :-( David, how long have you been seeing this ?
on and off for weeks, I think. I'll try with today's build.
this effects the WinNT M14 release build 2000022820.
*** Bug 30340 has been marked as a duplicate of this bug. ***
*** Bug 30722 has been marked as a duplicate of this bug. ***
*** Bug 32240 has been marked as a duplicate of this bug. ***
works with today's build.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WORKSFORME
verified: working with NT 2000050412
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.