Databases
StackOverflow2013
Postsdbo
POSelenium ElementNotVisibleException when enclosing div has transform applied
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSelenium ElementNotVisibleException when enclosing div has transform applied
    text
    copied!<p>I am using Intel's <a href="http://html5dev-software.intel.com/documentation/index.html" rel="nofollow">html5 app development framework</a>. Particularly, I am using <a href="https://github.com/01org/af-carousel" rel="nofollow">their carousel plugin</a>. But I suspect knowledge of webdriver is more useful here.</p> <p>The way their carousel works is that the pages float next to each other inside a div which has a limited width and overflow hidden. You can only see one of the pages at a time through the div "viewport".</p> <p>When you touch to move to the next div, it applies a css transform to animate sliding the page divs past. This works fine. However webdriver has trouble with elements inside the animation div.</p> <p>When you are on the first page, selenium reports all elements (on both pages) as displayed, even though half of them are hidden. Once you have transitioned to the second page, selenium reports all elements (on both pages) as not displayed.</p> <p>I tracked it down to this css property that gets applied to the animation div:</p> <pre><code>-webkit-transform: translate3d(-1024px, 0px, 0); </code></pre> <p>When this is applied, selenium thinks this element is invisible. When I remove it using Chrome developer tools, it thinks they are all visible.</p> <p>Two ways you might be able to help me:</p> <ul> <li>Can I get selenium to report correctly the visibility of these elements? Perhaps by tweaking the way the carousel works? (It is open source).</li> <li>Can I tell selenium to just click the element anyway, even though it is "not visible"?</li> </ul>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload