Closed
Bug 1216665
Opened 9 years ago
Closed 9 years ago
Disable asyncInit in 42
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(firefox42 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox42 | --- | fixed |
People
(Reporter: bugzilla, Assigned: bugzilla)
Details
Attachments
(1 file)
|
1.26 KB,
patch
|
bugzilla
:
review+
Sylvestre
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Given the Window neutering churn in 42, I am hesitant to ship 42 and asyncInit in one go. I think that it is safer to release with the updated neutering code in 42 and follow that up with full asyncInit in 43.
|
Assignee | |
Comment 1•9 years ago
|
||
|
|
Assignee | |
Comment 2•9 years ago
|
||
Comment on attachment 8676392 [details] [diff] [review]
Patch
doing r=me given it's just a pref change
Approval Request Comment
[Feature/regressing bug #]: plugin async init
[User impact if declined]: unknown side effects of neutering changes + async init
[Describe test coverage new/current, TreeHerder]: Plugin test suite
[Risks and why]: Low, was already disabled on Nightly and Aurora, and disabled in 41 release
[String/UUID change made/needed]: None
Attachment #8676392 -
Flags: review+
Attachment #8676392 -
Flags: approval-mozilla-beta?
|
||
Comment 3•9 years ago
|
||
Comment on attachment 8676392 [details] [diff] [review]
Patch
Sure, should be in 42 beta 9!
Thanks again for all your help and work on this feature!
Attachment #8676392 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
|
|
||
Updated•9 years ago
|
status-firefox42:
--- → affected
|
||
Comment 4•9 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
|
||
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•