541498 - Can't double-click to open html files with spaces in the filename

Status: VERIFIED DUPLICATE of bug 530064

(Firefox :: File Handling, defect)

Description

[Devon Hubbard]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

Firefox 3.6 isn't opening html files that contain spaces in their filename *when* the file is attempted to be opened by double-clicking on the file in the Finder, or drag-n-dropping onto the Firefox app icon or Firefox in the dock.

Reproducible: Always

Steps to Reproduce:
1) Use any html file as a sample file (encoding doesn't matter. e.g. UTF-8, UTF-16, Latin-1, bom, no bom, etc).
2) Rename the file to contain spaces in the name.
3) Double-click on the file (if Firefox is default browser), or drag-n-drop to Firefox app icon (in dock or directly onto app icon).
Actual Results:  
Result:
The file will not open and display in Firefox 3.6.

4) Remove or replace any spaces in the filename with a character, and double-clicking or drag-n-drop opens and displays the file.



Expected Results:  
drag-n-drop or double-clicking on html file should open and display in Firefox 3.6.


Note:
Using 'File > Open File' to open the file works.  It's only drag-n-drop or double-click that isn't opening files with spaces in the filename.

Regression note:
File opens and displays in Firefox 3.5.x without any problems.

Comment 1

[Devon Hubbard]

Turns out that any spaces in the files path will prohibit the file from being opened via drag-n-drop or double-click.  Of course, that makes sense given the entire filepath is the needed reference to open.

Example:
1) place a html file titled 'sample.html' on your desktop.
2) Double-click on it.  If Firefox 3.6 is your default browser, it will open and display.
3) In the Finder, press CMD+N to create a new folder.  The Finder will create a folder titled, "untitled folder".
4) Place the 'sample.html' file in that new folder.
5) Double-click on the 'sample.html' file.  

Result:
It won't open.  Rename the folder, 'untitled_folder' and try again.  The file will open now.

Comment 2

[EstherDavid Steffens]

Also Reproducible Always on Mac OS 10.5.8.

Devon Hubbard 2010-01-22 13:59:36 PST wrote:
> Note: Using 'File > Open File' to open the file works.

TRUE if you meant that you can open pathnames containing embedded spaces using the Firefox 'File' menu. NOT TRUE if you use Finder 'File > Open File', either Menubar or Contextual. That FAILS consistently, just like double-click to open.

NOTE: *NOT* just a Finder bug. Also adversely affects apps that send HTML files to the default browser for rendering, e.g. Mailsmith, which sends HTML email as a file named "HTML Enclosure.html". Note embedded space in name. That's how I discovered this bug. A royal pain. May mean that I will have to roll back to 3.5.X until this is fixed.

Comment 3

[Devon Hubbard]

Yes, to confirm, I did mean Firefox's 'File > Open File' menu item.  Thanks.  Sorry I wasn't more clear about that.  :-)

fwiw, myself and a few others I work with have already rolled back to 3.5.7 because of this bug.  we have too much html build output from our automated builds that can't be easily double-clicked on and opened with FireFox 3.6.

Comment 4

[philippe (part-time)]

dupe of bug 530064 ?

Comment 5

[EstherDavid Steffens]

(In reply to comment #4)
> dupe of bug 530064 ?

Yes, I agree.

Please excuse. I'm a newbie. Dunno how this system works, so I have to ask... When will that fix get into the 3.6.X production release?

Reason I ask... This bug adversely affects many Mac apps that send HTML files to the default browser for rendering. Found at least 5 other users complaining about this in the support Forum. And that's just today's postings. Apps affected include at least Mailsmith and Eudora. Possibly Dreamweaver. And then there are folks (like Devon, above) who need double-click to work. We all may have to roll back to 3.5.X until this is fixed in the 3.6.X producton release, or wait for 3.7, 'cuz this is a BAD bug to try to live with.

Comment 6

[philippe (part-time)]

(In reply to comment #5)
> (In reply to comment #4)
> > dupe of bug 530064 ?
> 
> Yes, I agree.
> 
> Please excuse. I'm a newbie. Dunno how this system works, so I have to ask...
> When will that fix get into the 3.6.X production release?
No idea, the bug has 3.6.x in the whiteboard; I guess, it will land sooner than later - esp if lots of people are affected.

Comment 7

[Stefan [:stefanh]]

(In reply to comment #5)
> (In reply to comment #4)
> > dupe of bug 530064 ?
> 
> Yes, I agree.
> 
> Please excuse. I'm a newbie. Dunno how this system works, so I have to ask...
> When will that fix get into the 3.6.X production release?

The patch in bug 530064 has the approval-1.9.2.1? flag. Once that is approved (a driver changes the flag to approval-1.9.2.1+), it will be ok to check-in the patch into the codebase that the Firefox 3.6.x releases are based on.

Comment 8

[Devon Hubbard]

verified dup