Hide
This idea originally came from Patrick Lightbody:
The need has come for Selenium to use cross-domain AJAX and, surprisingly, there is nothing out there that offers a simple interface similar to XHR that provides cross-domain AJAX support. That is unfortunate, because we can't simply plop in dojo or DWR inside of Selenium as it could easily clash with different versions of those frameworks in the application under test.
So my question is: how hard would it be to modify DWR and/or add a feature that made namespacing the objects in engine.js and SomeInterface.js in to a "Selenium." namespace, thus ensuring Selenium's engine.js did not collide with the AUT's? If this is pretty simple to do, I'd like to seriously discuss the possibility of using DWR as the core engine for automating Selenium's communication back and forth as it drives a test. Let me know.
Show
This idea originally came from Patrick Lightbody:
The need has come for Selenium to use cross-domain AJAX and, surprisingly, there is nothing out there that offers a simple interface similar to XHR that provides cross-domain AJAX support. That is unfortunate, because we can't simply plop in dojo or DWR inside of Selenium as it could easily clash with different versions of those frameworks in the application under test.
So my question is: how hard would it be to modify DWR and/or add a feature that made namespacing the objects in engine.js and SomeInterface.js in to a "Selenium." namespace, thus ensuring Selenium's engine.js did not collide with the AUT's? If this is pretty simple to do, I'd like to seriously discuss the possibility of using DWR as the core engine for automating Selenium's communication back and forth as it drives a test. Let me know.
New Feature
Open
Minor