1379490, 1392281, 1392318, 1392323, 1392339, 1392346, 1393812, 1394849, 1394881, 1400256, 1404946, 1405004, 1408454, 1409379, 1422593, 1422915, 1423209, 1423282, 1423356, 1423357, 1423358, 1423359, 1426154, 1429082, 1429083, 1429091, 1429111, 1429116, 1429199, 1430077, 1430109, 1430119, 1431155, 1431462, 1432212, 1432538
When a browser goes through the painful process of a remoteness change, its outerWindowID that we use as the WebDriver window handle also changes. This means users cannot rely on the window handle to stay consistent. This is a violation of the “unique resource identifier” a window handle should be mandated by the WebDriver specification. mconley mentions in https://bugzilla.mozilla.org/show_bug.cgi?id=1259055#c22 that we could use a <xul:browser>’s permanentKey as a replacement, as they are transferred when a browser is torn out to a new window.
Andreas, it would be good if you could wait for bug 1124604 being landed, which also includes a couple of changes to browser.js and also adds a couple of new tests. I'm planning to finish the patch today. Thanks.
Keywords: ateam-marionette-server, ateam-marionette-spec
Thank you for sharing the WIP. There are some parts we might want to discuss especially the different context classes and which methods those offer. I see upcoming conflicts for different applications. But maybe it's too early, and you still have considered to move around once the initial code is working. Otherwise lots of work done already!
Attachment #8893591 - Attachment is obsolete: true
Created attachment 8940312 [details] [diff] [review] 0001-Bug-1311041-wip.patch
Attachment #8899161 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.