RemoteNewTabLocation is assumed to be a singleton. But since newTab.js runs in a content frame, it creates a new instance of RemoteNewTabLocation. In order to get this working correctly, newTab.js needs to talk to the parent process' instance via message passing
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.