Closed Bug 444312 Opened 17 years ago Closed 17 years ago

losslessDecodeURI should accept strings

Categories

(Firefox :: General, defect)

defect
Not set
trivial

Tracking

()

RESOLVED INVALID

People

(Reporter: dao, Assigned: dao)

Details

Attachments

(1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
If you have a string that's most definitely a URI, there's no point in creating a nsIURI object just so that losslessDecodeURI can access |aURI.spec|. losslessDecodeURI should accept strings just like decodeURI.
Attachment #328656 - Flags: review?(gavin.sharp)
Oh, unfortunately, textValue isn't used for URI strings only. I can still see use cases for accepting plain strings, but if we don't have a consumer for that, it's not worth it...
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Attachment #328656 - Attachment is obsolete: true
Attachment #328656 - Flags: review?(gavin.sharp)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: