Closed Bug 182511 Opened 22 years ago Closed 22 years ago

Javascript error with layers loading page

Categories

(Core :: DOM: HTML Parser, defect)

Other Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: Ricardo.Salgado, Assigned: harishd)

References

()

Details

(Whiteboard: [Bug is with 1.2 builds only; site loads fine with trunk builds])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126 In the page at http://www.vizzavi.pt/, with Mozilla release 1.2, a Javascript error occurs: "There seems to be a error with this layer". The error did not occur in previous versions. Tried 1.1 Reproducible: Always Steps to Reproduce: 1. Just go to http://www.vizzavi.pt/ Actual Results: Javascript error occurs: "There seems to be a error with this layer". Expected Results: Load the page correctly as in previous versions.
Server seems to be down.
I can reproduce this on 1.2 final. It works as expected the trunk from a few days ago (both Win98). Bug 182500 may (or indeed may not) explain it, but it seems to share many features with the bugs marked as dependencies (javascript related, work on trunk, does not work on 1.2). Of course if it also broken on a newer trunk build then it's not related to 182500.
This is 1.2-branch only. See bug 182500.
Depends on: 182500
Version: Trunk → Other Branch
Confirming based on two separate reports above. Reassigning to Parser for parity with bug 182500 -
Assignee: rogerl → harishd
Status: UNCONFIRMED → NEW
Component: JavaScript Engine → Parser
Ever confirmed: true
QA Contact: pschwartau → moied
Whiteboard: [Bug is with 1.2 builds only; site loads fine with trunk builds]
I have tested that this bug was an instance of bug 182500 / bug 182253 based on comparison of two Linux builds compiled with gcc 3.2. This bug was present in the 1.2 release and was the only bug fixed in the 1.2.1 release (and the reason for the 1.2.1 release). Marking this bug as fixed since it should be fixed in the 1.2.1 release.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.