Chimera-only - tries to save data URLs w/o a media type

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
16 years ago
15 years ago

People

(Reporter: benc, Assigned: mikepinkerton)

Tracking

Details

(URL)

(Reporter)

Description

16 years ago
Chimera 0.6 vs. Mozilla 1.3a
STEPS:
data: URLs that work in Mozilla (display the expected text), go to the save
dialog  box in Chimera).

click on the URL provided.

EXPECTED EHAVIOR:
"test" should appear in your window.

OBSERVED BEHAVIOR:
Chimera tries to save a file w/ the text "test" to your drive.

The data URL format is both hard to read and parse because it has a really lame
double-parameter format deliniated w/ ";".

The format is of a fully legal URL is:

data:text/plain;charset=US-ASCII;base64,data

They try to justify that having two params is not going to confuse the data
scheme-specific parser by saying:

   The ";base64" extension is distinguishable from a content-type	
   parameter by the fact that it doesn't have a following "=" sign.

(You already cannot use a CISS hierarchical URL parser because they declared it
as having no relative formats).

That is all well and good, except we have equally lame error handling, so it is
hard to tell why these data URL's misbehave, but the rest of the test suite worked.

Here's my best guess:

If there is NO ";", then Chimera is fine:

data:,test

If there is a ":', but the media field is in use, everything is fine:

data:text/plain;base64,VGhpcyBpcyBhIHRlc3QK

If there is a null media field (characters between ":" and ";" then the problem
occurs.

data:;base64,VGhpcyBpcyBhIHRlc3QK -> download screen.

---
So when the media is empty, I don't know what we do here, does it go to unknown
content handler which is different in Chimera, or is it simply dumped to disk?
->d/l
Assignee: saari → sdagley
Component: General → Downloading
QA Contact: winnie → petersen

Comment 2

15 years ago
-> pinkerton
Assignee: sdagley → pinkerton
(Assignee)

Comment 3

15 years ago
wfm with a nightly
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.