Closed
Bug 1347515
Opened 8 years ago
Closed 7 years ago
Remove nsIJSON
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
People
(Reporter: hsivonen, Assigned: baku)
References
(Blocks 1 open bug)
Details
(Keywords: dataloss)
Attachments
(5 files, 1 obsolete file)
5.35 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
1.79 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
17.62 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
26.20 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
4.33 KB,
patch
|
jorgk-bmo
:
review+
|
Details | Diff | Splinter Review |
We should remove nsIJSON once support for XPCOM extensions has been dropped.
Updated•8 years ago
|
Priority: -- → P3
Blocks: post-57-api-changes
No longer depends on: post-57-api-changes
Updated•7 years ago
|
Whiteboard: [qf]
Updated•7 years ago
|
Whiteboard: [qf] → [qf-]
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → amarchesini
Assignee | ||
Comment 4•7 years ago
|
||
Attachment #8926830 -
Flags: review?(kyle)
Assignee | ||
Comment 5•7 years ago
|
||
Attachment #8926831 -
Flags: review?(kyle)
Assignee | ||
Comment 6•7 years ago
|
||
Attachment #8926832 -
Flags: review?(kyle)
Assignee | ||
Comment 7•7 years ago
|
||
Attachment #8926833 -
Flags: review?(kyle)
Assignee | ||
Updated•7 years ago
|
Attachment #8926831 -
Attachment description: nsIJSON.decodeToJSVal → part 2 - nsIJSON.decodeToJSVal
Updated•7 years ago
|
Attachment #8926830 -
Flags: review?(kyle) → review+
Updated•7 years ago
|
Attachment #8926831 -
Flags: review?(kyle) → review+
Comment 8•7 years ago
|
||
Comment on attachment 8926832 [details] [diff] [review] part 3 - nsIJSON.decodeFromStream Review of attachment 8926832 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/contextualidentity/ContextualIdentityService.jsm @@ +316,5 @@ > .createInstance(Ci.nsIFileInputStream); > inputStream.init(new FileUtils.File(this._path), > FileUtils.MODE_RDONLY, FileUtils.PERMS_FILE, 0); > try { > + let data = jSON.parse(NetUtil.readInputStreamToString(inputStream, I don't think this will run correctly? jSON shouldn't be valid?
Attachment #8926832 -
Flags: review?(kyle) → review-
Updated•7 years ago
|
Attachment #8926833 -
Flags: review?(kyle) → review+
Comment 9•7 years ago
|
||
Most everything looks good here, and will r+ pretty quick after that JSON typo is fixed.
Assignee | ||
Comment 10•7 years ago
|
||
Yes, I haven't pushed the patch to try. This is green.
Attachment #8926832 -
Attachment is obsolete: true
Attachment #8926967 -
Flags: review?(kyle)
Updated•7 years ago
|
Attachment #8926967 -
Flags: review?(kyle) → review+
Assignee | ||
Comment 11•7 years ago
|
||
comm repository has to be updated. I have to admit that I have not tested this patch. Jorgk, can you please review and test this patch? Thanks.
Attachment #8927053 -
Flags: review?(jorgk)
Comment 12•7 years ago
|
||
Thanks, I will.
Comment 13•7 years ago
|
||
Pushed by amarchesini@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/a3c81ef73700 Get rid of nsIJSON.encodeFromJSVal, r=qdot https://hg.mozilla.org/integration/mozilla-inbound/rev/e26f2365ea7c Get rid of nsIJSON.decodeToJSVal, r=qdot https://hg.mozilla.org/integration/mozilla-inbound/rev/08f21a0e7ebe Get rid of nsIJSON.decodeFromStream, r=qdot https://hg.mozilla.org/integration/mozilla-inbound/rev/31b7eb194662 Get rid of dom/json, r=qdot
Comment 14•7 years ago
|
||
I think this means we can remove the special parsing code we had for this API from the JS engine.
Comment 15•7 years ago
|
||
Comment on attachment 8927053 [details] [diff] [review] comm Review of attachment 8927053 [details] [diff] [review]: ----------------------------------------------------------------- ::: chat/modules/imSmileys.jsm @@ +5,5 @@ > Components.utils.import("resource:///modules/imServices.jsm"); > +Components.utils.import("resource://gre/modules/XPCOMUtils.jsm"); > + > +XPCOMUtils.defineLazyGetter(this, "gTextDecoder", () => { > + return new TextDecoder(); Why do it like this when you're doing it differently in calendar/test/unit/head_consts.js?
Assignee | ||
Comment 16•7 years ago
|
||
> Why do it like this when you're doing it differently in
> calendar/test/unit/head_consts.js?
This is for testing. We don't care too much of avoiding creating a single TextDecoder. But for imSmileys.jsm, we can optimize the number of TextDecoder objects.
Assignee | ||
Comment 17•7 years ago
|
||
(In reply to Tom Schuster [:evilpie] from comment #14) > I think this means we can remove the special parsing code we had for this > API from the JS engine. Can you file a follow up? Maybe pointing to the code you are talking about? Thanks
Flags: needinfo?(evilpies)
Comment 19•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a3c81ef73700 https://hg.mozilla.org/mozilla-central/rev/e26f2365ea7c https://hg.mozilla.org/mozilla-central/rev/08f21a0e7ebe https://hg.mozilla.org/mozilla-central/rev/31b7eb194662
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox58:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
Comment 20•7 years ago
|
||
Comment on attachment 8927053 [details] [diff] [review] comm Thanks, I'll get this landed now. Sadly we're busted by the packaging changes also landed here, so I can't test it. So we might have to follow up in case of problems.
Attachment #8927053 -
Flags: review?(jorgk) → review+
Comment 21•7 years ago
|
||
Pushed by mozilla@jorgk.com: https://hg.mozilla.org/comm-central/rev/ebac2c6a8ba8 remove dom_json.xpt from TB/IB/SM package manifests. rs=bustage-fix https://hg.mozilla.org/comm-central/rev/916c30e50af1 Remove use of nsIJSON in Thunderbird's calendar and chat. rs=jorgk
Comment 22•7 years ago
|
||
This regressed containers: https://github.com/mozilla/multi-account-containers/issues/949#issuecomment-343994922
Flags: needinfo?(amarchesini)
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(amarchesini)
Comment 23•7 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #22) > This regressed containers: > https://github.com/mozilla/multi-account-containers/issues/949#issuecomment- > 343994922 Can we pull this out of the first beta because of the regression? And then land it as part of the second beta that goes out, along with bug 1416468? If this goes into beta, it will cause irrevocable damage to Containers beta users. (20% of folks who have installed https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ are on beta.) Alternatively, we would have to get bug 1416468 into the first beta, and it might be too late for that.
Comment 24•7 years ago
|
||
Julien - Data loss in profile here, so we probably should take some action here quickly. We should probably rebuild beta 3 and retest even if that causes some delay in 58.0b3 release.
Flags: needinfo?(jcristau)
Keywords: dataloss
Comment 25•7 years ago
|
||
A note to clarify what landed where. We build 58.0b1 and shipped it last Tuesday to dev edition users. Because of some build issues we didn't ship 58.0b2. 58.0b3 in theory would ship this Wednesday to beta users for the first time. So, this regression was never shipped to non-nightly users.
Comment 26•7 years ago
|
||
This cause bug 1416468 regression. Back out first for the first 58 beta.
Comment 27•7 years ago
|
||
This shouldn't have landed during a Nightly soft freeze right before the final merge to Beta. Anyway, backout pushed to Beta. https://hg.mozilla.org/releases/mozilla-beta/rev/f7eb3bbcd5f830244a4234b1269c3a73e750330b
status-firefox59:
--- → fixed
Updated•7 years ago
|
Flags: needinfo?(jcristau)
Comment 28•7 years ago
|
||
Backed out from comm-beta (TB 58): https://hg.mozilla.org/releases/comm-beta/rev/778fc98a593fac351fedb4477fd2ce39629bc9cd https://hg.mozilla.org/releases/comm-beta/rev/b4b33e1604e113149a9c5401f8248b687a0dd79e
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
You need to log in
before you can comment on or make changes to this bug.
Description
•