I suggest you ...

Allow access to the driver under Fluent Automation

We are using Selenium driver with Chrome and we have to "scrollTo", but the API does not allow it.

We need it because we have to click on a link under a static positioned element, which gives a "Element not clickable at point ..." like here http://code.google.com/p/selenium/issues/detail?id=2766.

At first, I thought it would be great to add "scrollTo" in the API, but I'm sure I'll encounter other cases that are not in the API. The best solution in my view would be to allow a direct access to the driver that is used. In our case, Selenium / Chrome.

40 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Antoine LeclairAntoine Leclair shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Brijesh BharadwajBrijesh Bharadwaj commented  · 

        And i would like to respond to browser alerts, but i can't , small things like this are preventing me from switching over from out current custom wrappers around selenium.

        So atleast exposing the driver in some way so that we can write the necessary wrappers ourself would be a great boon.

      Feedback and Knowledge Base