Similar to bug 1322383 but for the listener.js framescript. Right now we do not always check for a valid top-level browsing context. Which means in case of navigating away from a frame, which might close it, following commands can fail because the context is no longer available. In those cases each of the methods should throw a NoSuchWindowException.
I don’t understand the description of this bug. Before a command request reaches the frame script, chrome space checks that the browsing context is still open. This returns a no such window error. Is that not sufficient?
I think that bug 1368492 actually should have implemented that from the chrome site.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1368492
You need to log in before you can comment on or make changes to this bug.