Closed
Bug 1456048
Opened 7 years ago
Closed 7 years ago
ChromeUtils.requestPerformanceMetrics is not threadsafe but is defined in Worker scopes
Categories
(Core :: DOM: Content Processes, defect, P3)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla61
| Tracking | Status | |
|---|---|---|
| firefox61 | --- | fixed |
People
(Reporter: kmag, Assigned: tarek)
References
Details
Attachments
(1 file)
No description provided.
|
Reporter | |
Updated•7 years ago
|
Flags: needinfo?(tarek)
|
Assignee | |
Comment 1•7 years ago
|
||
Sorry, I will move the definition to the [Exposed=(Window,System)] block
Assignee: nobody → tarek
Flags: needinfo?(tarek)
|
|
Assignee | |
Updated•7 years ago
|
Priority: -- → P3
| Comment hidden (mozreview-request) |
|
|
Assignee | |
Updated•7 years ago
|
Flags: needinfo?(kmaglione+bmo)
|
|
Reporter | |
Comment 3•7 years ago
|
||
| mozreview-review | ||
Comment on attachment 8970089 [details]
Bug 1456048 - move ChromeUtils.requestPerformanceMetrics to the right scope -
https://reviewboard.mozilla.org/r/238864/#review244774
Thanks
Attachment #8970089 -
Flags: review?(kmaglione+bmo) → review+
Pushed by tziade@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1048c4b6af7c
move ChromeUtils.requestPerformanceMetrics to the right scope - r=kmag
|
|
Assignee | |
Updated•7 years ago
|
Flags: needinfo?(kmaglione+bmo)
|
|
||
Comment 5•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•