477719 - JavaScript exception when opening an .eml message file [nsICommandLineHandler::handle]

Status: RESOLVED WORKSFORME

(MailNews Core :: Backend, defect)

Description

[IU]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090209 Lightning/1.0pre ID:20090209032350

This is a follow-on from Bug 476418.

Opening a .eml message file results in various JavaScript exceptions.

If Shredder is default email client and the .eml file is double-clicked (in
Windows Explorer) to open, the following exception occurs:

Error: [Exception... "'Failure' when calling method:
[nsICommandLineHandler::handle]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)" 
location: "<unknown>"  data: no]


Reproducible: Always

Steps to Reproduce:
1. Save the attached email somewhere on your filesystem
2. Open Error Console and scroll to bottom
3. Double-click sample.eml and note the exceptions in Error Console
4. Click File --> Open Saved Message..., browse to and open sample.eml.  Note
the exception.

Actual Results:  
Bug 466959 reports the same error, but the outcome described is slightly different.

Comment 1

[IU]

Regressed starting: version 3.0a1pre
(2008041103)

Comment 2

[IU]

Attachment: Sample email file

Comment 3

[Magnus Melin [:mkmelin]]

Confirmed - though is it really a regression? I think it's been happening quite some time.

Comment 4

[IU]

(In reply to comment #3)
> Confirmed - though is it really a regression? I think it's been happening quite
> some time.

Yes. It is a regression.  See Comment #1.  Unfortunately, I forgot to add the regression build and date when I initially filed so I added it in Comment #1.

Comment 5

[IU]

I'm no longer seeing this.  Not sure when it was fixed or by what.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090916 Lightning/1.0pre ID:20090916031343

Comment 6

[Magnus Melin [:mkmelin]]

->WFM (FIXED is only used when known code changes resolved the issue)
https://bugzilla.mozilla.org/page.cgi?id=fields.html#resolution