Closed Bug 19598 Opened 26 years ago Closed 26 years ago

[DOGFOOD] Can't read netscape web mail. Get a JS error

Categories

(Core :: DOM: HTML Parser, defect, P3)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Other
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: mscott, Assigned: rickg)

References

Details

(Whiteboard: [PDT+] 12/10)

I used to actually be able to sign on with a build from Saturday to my netcenter web mail account. But something changed between Saturday early evening and Monday morning that caused this regression. When I go to my netscape and click on web mail, instead of bringing up the web page where I can enter my password, I instead hit several warnings about null characters detected in a stream. And then I get eventually get a web page loade which says "Please enable java script in order to read your web mail" Or something like that. Adding norris to the cc list in case this is a JS security issue. Marking as dogfood as this is now blocking another dogfood nominated bug: Bug #19469
Blocks: 19469
CC'ing gagan, in case this has anything to do with the HTML mis-parsing we encountered recently. (Sorry, I looked for that bug, but I couldn't find it...)
Assignee: mccabe → rickg
Component: Javascript Engine → Parser
The warnings are from mozilla/htmlparser/src/nsScanner.cpp. The error window about JavaScript not being enabled comes up because the NOSCRIPT tag is not being interpreted properly, probably because of the null character problems. Forwarding to the parser component owner.
workaround (possibly,kinda): I got this same error trying to log into my.netscape.com. To log in, I logged in using netscape 4.x and copied my cookies file to mozilla's cookies file. Then, I didn't have to log in. Pretty lame, but it works. And it isn't just a one time solution (that would be pretty pointless), I don't have to log in ever again. I hope this works the same way with webmail.
Whiteboard: [PDT+]
Putting on PDT+ radar.
QA Contact: rginda → janc
Changing QA Contact to Jan
Cc:ing harishd, since he's recently dealt with NOSCRIPT elements in the content sink. As Norris suggested earlier, the problem is that we're parsing and processing the contents of the element.
Status: NEW → ASSIGNED
I just saw this today (11/29); I'll see what I can do.
Whiteboard: [PDT+] → [PDT+] I need feedback from vidur before est. a date.
Ok -- I'm waiting on feedback from vidur.
Target Milestone: M14
I think that http://bugzilla.mozilla.org/show_bug.cgi?id=20409 might be the same bug.
*** Bug 20409 has been marked as a duplicate of this bug. ***
Whiteboard: [PDT+] I need feedback from vidur before est. a date. → [PDT+] 12/10
*** Bug 20624 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed this by adding a hack to the parsing engine to drop no_script elements on the floor. I'll also open a new bug to fix the real problem after our dogfood release (to minimize risk).
Blocks: 21564
Status: RESOLVED → VERIFIED
No longer blocks: 21564
You need to log in before you can comment on or make changes to this bug.