Test JSON.parse with source edge cases
Categories
(Core :: JavaScript Engine, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: bthrall, Assigned: bthrall)
References
(Blocks 1 open bug)
Details
Attachments
(9 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
We want to make sure JSON.parse with source feature works at least in the following situations:
- Inside of Workers
- Interactions across multiple compartments (CCW, etc.)
- OOM behavior
- Exotic web platform objects (WindowProxy, cross-origin, etc.)
- X-rays
So we should add automated tests to verify that it does function as expected.
Assignee | ||
Comment 1•5 months ago
|
||
Assignee | ||
Comment 2•5 months ago
|
||
Assignee | ||
Comment 3•5 months ago
|
||
Assignee | ||
Comment 4•5 months ago
|
||
When --setpref is used, but --enable-json-parse-with-source is not, the custom
shell flag handling was overriding the --setpref value.
Assignee | ||
Comment 5•5 months ago
|
||
Note the raw
field is parsed as a number because JSON.stringify() serializes
RawJSONObject("4.32") as a number ('4.32') rather than a string ('"4.32"').
Assignee | ||
Comment 6•5 months ago
|
||
Using an IIFE lets me group the tests and name the group.
Assignee | ||
Comment 7•5 months ago
|
||
Assignee | ||
Comment 8•5 months ago
|
||
Assignee | ||
Comment 9•5 months ago
|
||
How the rawJSON
field should be handled isn't clear to me yet.
Changing set_spidermonkey_pref to always
is necessary for xpcshell to get the
pref value correctly. This is because xpcshell sets the prefs from
xpcshell.toml after the JS engine is initialized (via user.js);
experimental.json_parse_with_source is still false at that point.
Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Assignee | ||
Comment 10•5 months ago
|
||
It should be, according to
Updated•5 months ago
|
Comment 11•5 months ago
|
||
Comment 12•5 months ago
|
||
Backed out for causing mochitest plain failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/d63641241a5df86293ce726fa7a35787a6df8b35
Comment 13•5 months ago
|
||
Assignee | ||
Updated•5 months ago
|
Comment 14•5 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/318f2311a5e0
https://hg.mozilla.org/mozilla-central/rev/30bd191dca7d
https://hg.mozilla.org/mozilla-central/rev/12b1739f207e
https://hg.mozilla.org/mozilla-central/rev/29bae6b779a4
https://hg.mozilla.org/mozilla-central/rev/27bcb460dac2
https://hg.mozilla.org/mozilla-central/rev/57c453f97bcc
https://hg.mozilla.org/mozilla-central/rev/2635be086cf2
https://hg.mozilla.org/mozilla-central/rev/7d755d87bc7d
https://hg.mozilla.org/mozilla-central/rev/8405145a8468
Description
•