|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
59 bytes, text/x-review-board-request
|Details | Review|
Instead of passing capabilities to the content frame script when it attaches (Marionette:listnersAttached) we should either send the required information as part of the command IPC message or introduce a synchronous query service for the frame script to get the current capability state. For example, if a user calls the Set Timeouts command or a capability otherwise changes at runtime, between when a frame script has registered and an IPC message using this state is invoked, there is always a chance the capabilities cache in listener.js is outdated.
Summary: Query capabilities configuration from content frame script → Query capabilities configuration in frame script from chrome
Comment on attachment 8939367 [details] Bug 1379490 - Query capabilities configuration from chrome. https://reviewboard.mozilla.org/r/209738/#review216580
Attachment #8939367 - Flags: review?(dburns) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/2102ecc18aef Query capabilities configuration from chrome. r=automatedtester
Status: ASSIGNED → RESOLVED
Last Resolved: 5 months ago
status-firefox59: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in before you can comment on or make changes to this bug.