500151 - No access to named pipes via Javascript chrome extensions

Status: UNCONFIRMED

(Firefox :: File Handling, defect)

Description

[jm]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1) Gecko/20090616 Firefox/3.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1) Gecko/20090616 Firefox/3.5 (.NET CLR 3.5.30729)

In Windows, access to named pipes via chrome XUL Javascript extensions is not working:
var file = Components.classes["@mozilla.org/file/local;1"].
                     createInstance(Components.interfaces.nsILocalFile);
file.initWithPath("\\\\.\\pipe\\testpipe");
var foStream = Components.classes["@mozilla.org/network/file-output-stream;1"].createInstance(Components.interfaces.nsIFileOutputStream);

foStream.init(file, 0x02 | 0x08, -1, 0);

Results in an error (NS_ERROR_FAILURE), irrelevant to the open mode (read/readwrite/...).

Reproducible: Always

Steps to Reproduce:
1. Create a named pipe in an external application via kernel32's CreateNamedPipe
2. Try to open that pipe.

Actual Results:  
Exception NS_ERROR_FAILURE

Expected Results:  
Pipe can be opened and read/written to just like a file.

Pipe was created with PIPE_ACCESS_DUPLEX. Read other evidence that opening named pipes was not successfully possible.