Closed ahilss closed 10 years ago
It would be worthwhile testing with Electrolysis enabled in a current Nightly; it'll bump into issues similar to this one.
https://wiki.mozilla.org/Electrolysis https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox
@ahilss I love you
Yeah, thanks a ton for the fix!
On Oct 13, 2014, at 9:53 AM, Marco De Nadai notifications@github.com wrote:
@ahilss I love you
— Reply to this email directly or view it on GitHub.
Any idea when this fix might make it into a stable release? Especially considering we're up to Firefox 35 now o_0
Event objects passed into page_worker message handlers now appear to be immutable in FF32. We were mutating the event object by adding a setResponse function and replacing _callback_x strings in the message args with onSuccess and onError handlers. This is why we were seeing exceptions about onError being undefined. Making a deep copy of the message data fixes the issue.
It looks like events passed in contexts other than page_worker are still mutable, but we should still fix them to protect against changes like this in the future. Mutating input parameters is a bad idea, especially when those parameters come from third-party code.