Closed Bug 221097 Opened 21 years ago Closed 21 years ago

Loading page never finish using latest 1.6a (works well with v1.4 / v1.5rc2)

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: juloml, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031002 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031002 Loading http://www.root.cz never finish using latest 1.6a. this worked well using Mozilla 1.4 / 1.5rc2 Reproducible: Always Steps to Reproduce: 1. open url 2. wait 3. Actual Results: Browser doesn't load full page. worked using 1.5rc2 / 1.4
I've tested page using 1.6a 2003101304, Windows2000 and now loads fine. (In report i misspleed URL field, correct is http://www.root.cz)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 I have this problem with a lot of sites. If I leave the broswer and email open for a while say 30min plus with out doing anything. Then try and load a page it doesn't load the thorber just does it thing and nothing happens. If in email can't download email nothing happens. If trying to send email it says it can connect to the server. If I close Mozilla adn reopen everything just works fine and normally. Dave mozilla@karit.geek.nz
WFM using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031216 are there any other sites where this happens? if not, reporter, could you resolve the bug as WORKSFORME;
Page loading problem disappeared for me after using newer Mozilla build.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
(In reply to comment #3) > WFM using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031216 > > are there any other sites where this happens? > if not, reporter, could you resolve the bug as WORKSFORME; Today I upgraded to 1.0.4 (german). The bug is still present, just as it was with 1.0.3. The incident ID is: TB5768013M . I cannot find other sites triggering this behaviour. Is resolving the bug as WFM appropriate?
You need to log in before you can comment on or make changes to this bug.