Closed zacharyc closed 12 years ago
Zack, is this still reproducible? Is it a bug in chrome?
It is still reproducible. Think it is a bug in chrome, but would need to spend more time investigating.
This problem happened because chrome started treating "newtab" as a domain, with it's own domain restrictions. When we try to launch an application in the child window, we load a different domain, thus losing the ability to control the window. The problem was solved by simply loading the application URL in the base window. It's not elegant (we have two windows with the app now), but it works.
In Chrome Dev Channel, I ran into an issue whereby it screening was unable to find the interaction window. I reverted back to stable and was able to get the test working. This test was braking in screening on chrome dev channel