188450 - Mach-O: Browser should use HFS paths instead of POSIX paths when communicating with plugin

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect)

Description

[Jonathan Brecher]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030104
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030104

The Mach-O trunk build is sending paths to plugins in POSIX style
(/path/to/file.ext) rather than in HFS style (drive:path:to:file.ext).  Yes, a
smart plugin should be able to handle both, but this is a sudden change that's
limited to the Mach-O build, so I think it was probably not intended.

I found this issue when responding to an NPP_StreamAsFile call.  I didn't check
to see if there were any other places where the browser sends POSIX paths.

For reference, POSIX paths are *not* sent in the following cases:
The last CFM build I looked at (late december)
Chimera (a recent build, like a few days ago)
Safari

Reproducible: Always

Steps to Reproduce:

Comment 1

[Boris Zbarsky [:bzbarsky]]

confirming....

Comment 2

[Peter Lubczynski]

I think this has been recently fixed.

Reporter, can you test and close bug if fixed?

Comment 3

[Jonathan Brecher]

Sorry, no, I can't.  Scriptable plugin support on the Macintosh is a total mess.  
As a result we've been forced to shut down Macintosh plugin development and focus 
on more productive matters.  If you and Apple get your act(s) in gear, we will 
revisit the issue.

Comment 4

[Simon Fraser [no longer active]]

We're still passing POSIX paths (e.g. to NPP_StreamAsFile)

Comment 5

[Josh Aas]

We're not going to do this at this point.