57905 - uncaught exception in filepicker.js

Status: VERIFIED FIXED

(Core :: XUL, defect, P3)

Description

[Tom Everingham]

Overview Description:  I am getting an unhandled exception message when clicking 
a dangling symbolic link 

Steps to Reproduce:
1.)  Set up a directory with a symbolic link that does not point to anything.  
ie. delete the file it points to
2.)  click on the link

Actual Results:  I get the following javascript error in the console.
JavaScript error: 
 line 4: uncaught exception: [Exception... "Component returned failure code: 
  0x80520006 [nsIFile.isFile]"  nsresult: "0x80520006 (<unknown>)"  
  location: "JS frame :: chrome://global/content/filepicker.js :: onSelect 
  :: line 314"  data: no]

Expected Results:  should be handled (as in windows) as an error box with a file 
not found message.

Build Date & Platform Bug Found:  Linux rh6 10/24 branch

Additional Builds and Platforms Tested On:
Works on winNT

Comment 1

[R.K.Aa.]

Somewhat related to bug 56779 - adding bryner to CC.

Comment 2

[lchiang]

does this need to be rtm?  Looks like just an error is written out?

Comment 3

[Peter "jag" Annema]

We could try/catch the isFile() and isDirectory() calls, but those should really
not be giving that (known) error to start with.

bryner?

Comment 4

[Brian Ryner (not reading)]

I agree.  This is a problem with followLinks not being honored.  When I get
around to filing a bug for that, I'll mark this one as dependant.

Comment 5

[Tom Everingham]

I don't think it should be rtm'd.  You would run into this rarely.

Comment 6

[Brian Ryner (not reading)]

This exact exception is no longer applicable with the outliner rewrite, but
there's an analogous one which I've filed as bug 82832.

Comment 7

[sairuh (rarely reading bugmail)]

no longer see this in verif builds. see the exception noted in bug 82832 in
debug builds, though.