Closed
Bug 857715
Opened 12 years ago
Closed 12 years ago
testing/xpcshell/head.js should use 'uneval' to splice values into computed JS source
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla23
People
(Reporter: jimb, Assigned: jimb)
Details
Attachments
(1 file)
In testing/xpcshell/head.js, do_load_child_test_harness does various just-good-enough kludges to pass some string-valued parameters to the child process. However, the built-in 'uneval' function does exactly the sort of quoting that's needed here, and handles arrays automatically. do_load_child_test_harness should use 'uneval'.
Assignee | ||
Comment 1•12 years ago
|
||
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 732966 [details] [diff] [review]
In testing/xpcshell/head.js, use 'uneval' to quote values passed to the child process.
Try run looked good.
Attachment #732966 -
Flags: review?(benjamin)
Comment 3•12 years ago
|
||
Comment on attachment 732966 [details] [diff] [review]
In testing/xpcshell/head.js, use 'uneval' to quote values passed to the child process.
I'm going to forward this on to Ted as owner of the testing infrastructure, and he will probably forward it along to somebody else. Hot potato!
Attachment #732966 -
Flags: review?(benjamin) → review?(ted)
Comment 4•12 years ago
|
||
Comment on attachment 732966 [details] [diff] [review]
In testing/xpcshell/head.js, use 'uneval' to quote values passed to the child process.
Review of attachment 732966 [details] [diff] [review]:
-----------------------------------------------------------------
That's a much cleverer solution.
Attachment #732966 -
Flags: review?(ted) → review+
Updated•12 years ago
|
Assignee: nobody → jimb
Component: IPC → XPCShell Harness
Product: Core → Testing
Assignee | ||
Comment 5•12 years ago
|
||
Status: NEW → ASSIGNED
Flags: in-testsuite-
Target Milestone: --- → mozilla23
Comment 6•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•