crash when file upload name contains a single quote

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
critical
RESOLVED INCOMPLETE
13 years ago
11 years ago

People

(Reporter: Andrew Clements, Unassigned)

Tracking

({crash})

1.0 Branch
x86
Windows 2000
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Using Plone internally (plone.org), I go to upload a file and there is an HTML
form with an <input type="file">. When a file name containing a single quote is
added (eg: "c:\my folder\it's a nice file.pdf"), Firefox 1.0.6 instantly
disappears/crashes. There appears to be no pointer exception or the like, FF
just shuts down.

If I remove the single quote - no other changes, the file uploads OK.

There appears to be no Javascript (event triggered or otherwise) executed in the
for.


Reproducible: Always

Steps to Reproduce:
1. Access a HTML form containing a file upload input control
2. Specify a filename that contains a single quote
3. Submit the form

Actual Results:  
Firefox exits (very quickly)

Expected Results:  
File should have uploaded, or at least complained about a non-handled character


Windows 2000, Firefox 1.0.6, Thunderbird 1.0.6

Several Extensions installed, SessionSaver2.0.2 being the only one I can see
that may check page status on submit. Others are tools like "Web Developer",
Calendar etc.

Comment 1

13 years ago
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050808 Firefox/1.0+
ID:2005080814

This works fine for me. Do you see this in safe mode?
http://kb.mozillazine.org/Safe_mode, if so, do you see this in the latest
builds? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Updated

13 years ago
Keywords: crash
Version: unspecified → 1.0 Branch
resolving as incomplete since missing feedback for comment #1.

Andrew, if you still see this error in a recent release, feel free to reopen
this bug. It would be great if you could answer comment #1 with the questions
from  jesse then. 
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.