Closed Bug 417386 Opened 18 years ago Closed 13 years ago

Incorrect uneval of E4X object containing line break

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
minor

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: testcase)

js> var u = uneval(<xxx>{function(){}}</xxx>); js> u; <xxx>function () { }</xxx> js> eval(u); typein:11: SyntaxError: syntax error: typein:11: }</xxx> typein:11: ^
{ and } are special characters in E4X for interpolating computed values, e.g. <x>foo</x> is equivalent to <x>{"foo"}</x>, so we should be converting the braces to entities here.
(In reply to comment #2) How is bug 497149 a dupe of this bug? It looks like this bug is just about escaping curly braces. Bug 497149 is about "\\n" being put in processing instructions' .toString() output instead of "\n".
e4x is being removed (bug 788293).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.