Patch for "master" branch: https://reviews.mahara.org/6492
-- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1582535 Title: Behat "Element is not clickable" error when a page is too long to fit in the window Status in Mahara: New Bug description: I noticed this while working no the Behat tests for threaded comments. Once I had enough comments that some of them were below the bottom of the page, I would get this error whenever I ran the automated tests: When I delete the "Comment 1-1." row # BehatGeneral::i_delete_the_row() Element is not clickable at point (905, 12.300003051757812). Other element would receive the click: <div class="site-message alert alert-info" role="alert"></div> Command duration or timeout: 78 milliseconds Build info: version: '2.52.0', revision: '4c2593c', time: '2016-02-11 19:06:42' System info: host: 'vegas', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-86-generic', java.version: '1.7.0_21' Session ID: 6c32356d-5179-4612-99ee-e15f3ec90c83 Driver info: org.openqa.selenium.firefox.FirefoxDriver Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, cssSelectorsEnabled=true, databaseEnabled=true, browserName=firefox, handlesAlerts=true, nativeEvents=false, webStorageEnabled=true, rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true, takesScreenshot=true, version=46.0}] (WebDriver\Exception\UnknownError) Confusingly, if I put a pause in the test and manually inspected the page, I could see that the element was visible, and if I let the test resume after pausing, it always worked! But then when running by itself, without me manually inspecting it, it would crash again. Eventually I realized this is because the Behat Mink Selenium webdriver we're currently using, is trying to click on the element like a mouse would, rather than firing a "click" event like jQuery would do. And, because I had made several comments, the button I wanted to click on was not actually visible in the window. When I manually inspected it, I scrolled the button into the window, which is why it worked. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1582535/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
