Closed
Bug 18948
Opened 25 years ago
Closed 25 years ago
can't scroll or click on link while page is loading.
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: mahjongg, Assigned: leger)
Details
While a page is loading (the "barperpole" is turning) I can't drag the page down
nor can I click on a link (cursor does not turn into a hand when hovering over
the link).
At first I thought this was an intentional temporary "fix" for other problems
but I cannot find any reference to this phenomenon here.
After the barberpole stops moving everything is normal.
I am using build 1999111218
Now using Milestone 11, this bug is still the one thing (except for occasional
crashes) that makes Mozilla unusable! Every time i go to a new website i have to
wait untill the _whole_ page is received before i can start scrolling the page.
On a longer page this means that I have to wait minutes before I can scroll the
page down. The problem might be related to the fact that I have a relatively
high speed ISDN connection. Another symptom is that for a longer page the
barberpole and mozzilla logo's are not animated, as if the CPU is starved for
cycles so it does not have the time to animate them. If I click on the scrollbar
sometimes it turns black and i see some "snow" in it as if it is constantly
being rewritten. Occasionally The page _will_ scroll, just before the barberpole
disappears and "Document Done" appears, after wich I can scroll the page as normal.
The problem is _not_ confined to my computer, I have another computer at work,
(also using ISDN) that has the same behaviour. However I do not see anyone else
complaining about this bug so I assume it is not as common as it seems to be.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 2•25 years ago
|
||
Most likely duplicate of bug 17325. mahjongg@xs4all.nl: try a later build and
reopen bug if this is not fixed yet.
*** This bug has been marked as a duplicate of 17325 ***
Yes I agree that this problem is fixed now, and that it was propably the
incremental reflows that caused the problem.
Comment 4•25 years ago
|
||
Verified duplicate of 17325 -{sink}Limit number of incremental reflows-
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•