Closed
Bug 1814478
Opened 2 years ago
Closed 2 years ago
Use JS Context to do JSON parsing in the Utility Process
Categories
(Core :: DOM: Networking, task, P2)
Core
DOM: Networking
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: sefeng, Assigned: sefeng)
References
Details
(Whiteboard: [orb:m1][necko-triaged], [wptsync upstream])
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Priority: -- → P2
Whiteboard: [orb:m1] → [orb:m1][necko-triaged]
Assignee | ||
Comment 3•2 years ago
|
||
I plan to land the stuff for Javascript parsing first, and land the JSON stuff as a separate patch. So that's bug 1814478 for JSON, and bug 1809518 for javascript :)
Flags: needinfo?(sefeng)
Updated•2 years ago
|
Attachment #9315452 -
Attachment description: WIP: Bug 1814478 - Add JSON parsing to JS Validator r=farre,smaug,tcampbell! → Bug 1814478 - Add JSON parsing to JS Validator r=farre,smaug,tcampbell!
Comment 4•2 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:sefeng, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.
Flags: needinfo?(sefeng)
Flags: needinfo?(afarre)
Assignee | ||
Comment 5•2 years ago
|
||
This is on our radar.
Flags: needinfo?(sefeng)
Flags: needinfo?(afarre)
Pushed by sefeng@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1f3b1e93b0fa
Add JSON parsing to JS Validator r=farre,smaug,tcampbell
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/38792 for changes under testing/web-platform/tests
Whiteboard: [orb:m1][necko-triaged] → [orb:m1][necko-triaged], [wptsync upstream]
Comment 8•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•