Closed Bug 2325 Opened 26 years ago Closed 26 years ago

Page reports Javascript not enabled

Categories

(Core :: DOM: Core & HTML, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: michael.j.lowe, Assigned: rickg)

References

()

Details

"Your browser reports that JavaScript is not enabled. This Web site requires that both JavaScript and Java be enabled"
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA Contact: 4015 → 4616
QA contact re-assigned according to the product areas we're currently working on.
Component: DOM Level 1 → DOM Level 0
Component updated to DOM Level 0.
Assignee: vidur → kipp
Target Milestone: M4 → M5
Looks like they've changed the site quite a bit. Right now, I hit an assertion in layout code in nsBlockFrame::DoRemoveFrame() (probably since I don't have the Java plugin installed and the APPLET). Kipp, if we can get past this error and there are still JavaScript problems, feel free to assign it back to me.
Status: NEW → ASSIGNED
Priority: P2 → P1
At the moment, its crashing in the parser...
Assignee: kipp → rickg
Status: ASSIGNED → NEW
Here is what I see currently. The document loads in and a dump content shows nothing but a bunch of meta tags. However, the frameset in the page never loads, nor does the parser enable layout so all we end up with is an empty page...
Assignee: rickg → kipp
There is still one bug in the parser (it's moving the <NOSCRIPT> out of the head. But the crash is gone. Back to you.
Assignee: kipp → rickg
Taking this back until I can find out what went wrong.
Corrected by changes to parsing engine.
Status: RESOLVED → REOPENED
Original bug is still not fixed
Assignee: rickg → vidur
Status: REOPENED → NEW
Assignee: vidur → rickg
Damn, this bug has been around, hasn't it? Well, keeping with the trend... The problem is that we're parsing and dealing with the contents of the NOSCRIPT element. My impressions was that the parser stripped this out.
Status: NEW → ASSIGNED
Target Milestone: M6 → M7
Resolution: FIXED → ---
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
OK, the NOSCRIPT problem has been fixed and I'm going to close this bug. There are layout problems on the resulting page and I'll give them to Chris Karnaze.
Status: RESOLVED → VERIFIED
Verified.
You need to log in before you can comment on or make changes to this bug.