Use old escape/unescape for JavaScript <= 1.3

RESOLVED EXPIRED

Status

()

RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: bugzilla-mozilla-20000923, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
timeless had the idea that "old" JavaScript should get the old (NS4?)
escape/unescape functions, instead of the new ones.

Comment 1

15 years ago
The goal here would be to allow two scripts in a document access to the two
flavors of the function (a third untagged script could be used to drive the code
from the versioned scripts).  Doing this would enable people to easily decode
and reencode stored values for migration if they needed to. This also should be
more compatible with N4 as the 1.5 magic flavor wouldn't run at all. This isn't
limited to chrome or content specifically, it would be useful for both.
Those old escape and unescape functions were implemented in the DOM, and need to
be somewhere that knows the document's character set encoding.  This bug is
prolly in the wrong component, but it sounds like a good idea to me -- unless IE
provides only the new ECMA functions to the old JS versions.

/be
Assignee: general → general
Yeah, if this solves real problems I'd be happy to see a change like this go in
(heck, I could even offer to code it up :-), but does anyone know if this would
actually fix enough problems to bother?

Comment 4

14 years ago
prolly a wontfix due to "JS1.2 must die" Bug 255895
QA Contact: pschwartau → moz
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.