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

VERIFIED FIXED in M14

Status

()

P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: mscott, Assigned: rickg)

Tracking

Trunk
x86
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PDT+] 12/10)

(Reporter)

Description

19 years ago
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
(Reporter)

Updated

19 years ago
Blocks: 19469

Comment 1

19 years ago
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...)

Updated

19 years ago
Assignee: mccabe → rickg
Component: Javascript Engine → Parser

Comment 2

19 years ago
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.

Comment 3

19 years ago
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.

Updated

19 years ago
Whiteboard: [PDT+]

Comment 4

19 years ago
Putting on PDT+ radar.

Updated

19 years ago
QA Contact: rginda → janc

Comment 5

19 years ago
Changing QA Contact to Jan

Comment 6

19 years ago
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.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 7

19 years ago
I just saw this today (11/29); I'll see what I can do.
(Assignee)

Updated

19 years ago
Whiteboard: [PDT+] → [PDT+] I need feedback from vidur before est. a date.
(Assignee)

Comment 8

19 years ago
Ok -- I'm waiting on feedback from vidur.
(Assignee)

Updated

19 years ago
Target Milestone: M14

Comment 9

19 years ago
I think that http://bugzilla.mozilla.org/show_bug.cgi?id=20409 might be the
same bug.

Comment 10

19 years ago
*** Bug 20409 has been marked as a duplicate of this bug. ***
(Assignee)

Updated

19 years ago
Whiteboard: [PDT+] I need feedback from vidur before est. a date. → [PDT+] 12/10
(Assignee)

Comment 11

19 years ago
*** Bug 20624 has been marked as a duplicate of this bug. ***
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 12

19 years ago
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).

Updated

19 years ago
Blocks: 21564

Updated

19 years ago
Status: RESOLVED → VERIFIED

Updated

19 years ago
No longer blocks: 21564
You need to log in before you can comment on or make changes to this bug.