Aaron Gibralter 182cb2e5b7 Working on frame handling. In terms of the QT code, the non-frame-related ... specs pass with these changes (e.g. mainFrame() => currentFrame() and the new injectJavascriptHelpers() code in WebPage.cpp). It seems like the current JS+xpath implementation dives in to iframes already. Is this desired behavior? I wonder if that works with x-domain iframes? I doubt it... Also, this design assumes that we only step one frame down at a time... Lastly, I'm really not sure how QWebKit decides which frame is currentFrame(). For now, I'm hoping to be able to use the QWebFrame setFocus() method. This may be a dead end though. We may have to have WebPage manually keep track of the "current" frame.		2011-04-20 18:12:03 -04:00
..
capybara/driver	Working on frame handling. In terms of the QT code, the non-frame-related	2011-04-20 18:12:03 -04:00
capybara-webkit.rb	Initial commit	2011-02-24 23:13:11 -05:00
capybara_webkit_builder.rb	Move code that compiles Webkit into separate file to support Ruby 1.9.2	2011-04-15 17:53:31 -04:00