WebDriver confuses opacity: 0 with hidden

[lukeis]

Originally reported on Google Code with ID 1610

What steps will reproduce the problem?
1. Create an input and set opacity to 0
2. Using selenium, try to click the input
3. Selenium gives an error that the input is hidden. It is not -- it is simply invisible,
but the user can still interact with it in the browser.

What is the expected output? What do you see instead?
Expected output is to click the input. Instead, Selenium generates an error:
Element is not currently visible and so may not be interacted with (Selenium::WebDriver::Error::ElementNotDisplayedError)

What version of the product are you using? On what operating system?
Selenium 2 on OS X using Firefox.

Please provide any additional information below.
The reason opacity is set to zero is to cover up a file input with a different image.
The user clicks through the image to the invisible input. This is a very common practice
for styling file inputs, which are notoriously difficult to otherwise  customize.

Reported by neil.rotstan on 2011-04-29 21:31:54

[lukeis]

Indeed, this is a known issue that should affect any browser using the atoms. 

Reported by jari.bakken on 2011-04-30 15:52:51

• Status changed: Accepted
• Labels added: Component-WebDriver

[lukeis]

Reported by jari.bakken on 2011-04-30 15:53:27

[lukeis]

Issue 1550 has been merged into this issue.

Reported by jari.bakken on 2011-04-30 15:53:59

[lukeis]

Jason, looks like you added this behaviour in r10752. This is arguably the correct behaviour
for bot.dom.isShown, but then using that to limit clicking prevents users from performing
a perfectly valid interaction.

Thoughts?

Reported by jari.bakken on 2011-04-30 16:05:54

[lukeis]

bot.dom.isShown was changed in  r11353 to optionally exclude opacity when testing for
visibility.  The FirefoxDriver is not setting this optional flag when calling bot.dom.isShown

http://code.google.com/p/selenium/source/browse/trunk/javascript/firefox-driver/js/preconditions.js#63

Reported by jmleyba on 2011-05-02 17:27:21

[lukeis]

This issue was updated by revision r12138.

This is fixed for Firefox.  iOS and HtmlUnit also do the right thing.  IE still
needs to be fixed.

Reported by jmleyba on 2011-05-06 17:28:38

[lukeis]

Reported by jmleyba on 2011-05-06 17:29:28

[lukeis]

This issue was closed by revision r12148.

Reported by james.h.evans.jr on 2011-05-09 20:35:03

• Status changed: Fixed

[lukeis]

I don't understand what is the resolution of this issue. Using r.12239

I have 0 opacity for file input field because of styling (it's a very common practice
btw) and FiferoxDriver click() doesn't do anything, ChromeDriver 12.0.712.0 throws


org.openqa.selenium.ElementNotVisibleException: Element must be displayed

and HtmlUnitDriver throws :

org.openqa.selenium.NoSuchElementException: Unable to locate element with ID: myfile

I have entire websites styled like this ... Don't know what to do, please help

<label class="browse-button" id="aui_3_3_0_11593">
  <span id="aui_3_3_0_11592">
    <input type="file" multiple="" id="myfile" name="file">
  </span>Browse (you can select multiple files).
</label>

label.browse-button {
    width:120px;
    height:40px;
    overflow:hidden;
    position:relative;
    float: left;
    background-color:#ccc;
}

label span input {
    z-index: 999;
    line-height: 0;
    font-size: 50px;
    position: absolute;
    top: -2px;
    opacity: 0;
    filter: alpha(opacity = 0);
    -ms-filter: "alpha(opacity=0)";
    cursor: pointer;
    _cursor: hand;
    margin: 0;
    padding:0;
}

Reported by liska.jakub on 2011-05-25 09:22:00