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
..
integration	support utf8 command ( ruby to webkit_server )	2011-04-19 20:51:38 +09:00
support	Fixed multiple browsers starting because before(:all) runs multiple times; fixed separate app servers starting for each example; added injectable class for debugging wire protocol	2011-03-11 11:19:59 -05:00
driver_spec.rb	Working on frame handling. In terms of the QT code, the non-frame-related	2011-04-20 18:12:03 -04:00
spec_helper.rb	Wait and timeout when looking for content	2011-04-14 10:16:56 -04:00