Thanks for the explanation, Jason - that helps a lot. We'll see if we can get something working with that angle. I'll post back to the list if we make any progress.
Drew On 8/2/05, Jason R Huggins <[EMAIL PROTECTED]> wrote: > > Hi, Drew, > > Selenium adds "event listeners" on page load events so it knows when to > continue running a test after waiting for a new page to load. > > Selenium would need to add an page load event listener on all nested frames > for this functionality to work. It's not impossible, but it would take work > to dynamically inspect all the frames of a given application and "tag" them > appropriately. > > The same goes for how Selenium finds elements in your application for > clicking, typing into, or verifying.... It expects a document to manipulate, > not a frameset, or mulitple frames to search for elements... > > If code was added to fix the page load event listener issue and the element > location searching issue... Selenium could support frames. > > - Jason > > Drew Cox wrote on 08/02/2005 10:43:33 AM: > > > Does anyone know if there *are* other issues to using frames that > > might not be immediately obvious? Anything that would make it > > particularly difficult? > > > > I'm going to be attempting frame testing today, so I'm guessing I'll > > probably have a better feel for what the challenge is very shortly. > > Any insights would be most appreciated though ;-) > > > _______________________________________________ Selenium-users mailing list [email protected] http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
