Closed
Bug 1261428
Opened 8 years ago
Closed 8 years ago
Replace an additional JS_ReportError
Categories
(Core :: DOM: Workers, defect)
Core
DOM: Workers
Tracking
()
RESOLVED
FIXED
mozilla48
Tracking | Status | |
---|---|---|
firefox48 | --- | fixed |
People
(Reporter: khuey, Assigned: khuey)
References
Details
Attachments
(1 file)
2.58 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
Now that we have infrastructure for this!
Attachment #8737294 -
Flags: review?(bzbarsky)
Comment 1•8 years ago
|
||
Comment on attachment 8737294 [details] [diff] [review] Patch r=me with a better commit message. That said, I looked at the use of aCx here, and it's shenanigans all the way. The only remaining consumer is the nsJSUtils::GetCallingLocation call when !newInfo->mTimeoutString.IsEmpty(). But if you look at the callers, the _Function_ overload of WorkerGlobalScope::SetInterval is what passes the caller JSContext (this is the case when it does not get used) while the string version passes GetCurrentThreadJSContext() for some bizarre reason. Same thing for WorkerGlobalScope::SetTimeout. Mind fixing that stuff to just pass through the JSContext without shenanigans?
Attachment #8737294 -
Flags: review?(bzbarsky) → review+
Comment 4•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9e574b87617b https://hg.mozilla.org/mozilla-central/rev/67f70018cbb5
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox48:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in
before you can comment on or make changes to this bug.
Description
•