Clicking <tr> with even number of <td>'s returns "Element is Obscured"

Confirmed Issue #5238133 • Assigned to Rick J.

Details

Created
Oct 29, 2015
Privacy
This issue is public.
Reports
Reported by 33 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

==============

click the element at id “inner_first” on this page-

https://github.com/watir/watirspec/blob/master/html/tables.html

Expected Results:

==============

If it is displayed it should be able to be clicked

Actual Results:

==============

Element is obscured error

Dev Channel specific:

================

Yes

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Mara P.”

      Changed Assigned To from “Mara P.” to “Ben B.”

      Changed Status to “Confirmed”

      Changed Title from “Edge Driver - Clicking Displayed Element Returning as Obscured” to “WebDriver - Clicking Displayed Element Returning as Obscured”

      Changed Title from “WebDriver - Clicking Displayed Element Returning as Obscured” to “Clicking Displayed Element Returning as Obscured”

      Changed Assigned To from “Ben B.” to “IE S.”

      Changed Status from “Confirmed” to “Not reproducible”

      Changed Assigned To to “Aditya K.”

      Changed Status from “Not reproducible”

      Changed Assigned To from “Aditya K.” to “Ben B.”

      Changed Status to “Confirmed”

    • I am running into the same issue, with a very simple test:

      UnknownError: [POST http://192.168.122.221:4444/wd/hub/session/9729c7e4-7cf1-41e2-b0cb-b36811a78d85/element/2/click] Element is obscured (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 14 milliseconds
      Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 17:00:58'
      System info: host: 'MSEDGEWIN10', ip: '192.168.122.221', os.name: 'Windows 10', os.arch: 'x86', os.version: '10.0', java.version: '1.8.0_77'
      Driver info: org.openqa.selenium.edge.EdgeDriver
      Capabilities [{applicationCacheEnabled=true, acceptSslCerts=true, browserVersion=34.14295.1000.0, platformVersion=10, locationContextEnabled=true, webStorageEnabled=true, browserName=MicrosoftEdge, takesScreenshot=true, pageLoadStrategy=normal, takesElementScreenshot=true, platformName=windows, platform=ANY}]
      Session ID: FD695E03-FDE3-43CB-B744-40CB94AA1AA8
        at runRequest  
        at 
        at new Promise  
        at ProxiedSession._post  
        at Element._post  
        at Element.click  
        at Command.  
        at 
        at run  
        at 
        at Command.target.(anonymous function) [as click]  
        at Test.registerSuite.Button [as test]  
        at 
        at 
        at runCallbacks  
        at 
        at run  
        at 
        at doNTCallback0  
        at process._tickCallback  
      
    • This seems like a complete showstopper, isn’t it? I’m also trying findByCssSelector and after finding the element, the click throws this same exception.

      Is there a work-around of some kind?

    • I’m running into this with checking a checkbox. I wanted to include edge but this is a show stopper.

    • I too, am experiencing the same issue via SauceLabs and the test is a simple login into the application. the click event throws the error.

    • Having this issue as well on Windows 10, 10586 with Microsoft Web Driver 2.0 (Fall 2015 Update). Using selenium on node.js.
      This affects all elements that I am trying to click, each of which are clearly visible and away from the sides of the screen. So it’s a complete show-stoppper as far as testing on Edge is concerned.

      Here is a sample of the Web API traffic (using >>> and <<< to indicate direction):

      >>>
      POST /session/0CEA7F27-EB9C-4FBF-97E3-481203F7D7AF/element HTTP/1.1
      accept: application/json; charset=utf-8
      {"using":"link text","value":"Site"}
      <<<
      HTTP/1.1 200
      content-type: application/json;charset=UTF-8
      server: Microsoft-HTTPAPI/2.0
      access-control-allow-origin: *
      date: Wed, 08 Jun 2016 00:36:45 GMT
      connection: close
      content-length: 199
      {"sessionId":"0CEA7F27-EB9C-4FBF-97E3-481203F7D7AF","status":0,"value":{"element-6066-11e4-a52e-4f735466cecf":"8493e4b2-ed09-4653-a005-2a07d64b785c","ELEMENT":"8493e4b2-ed09-4653-a005-2a07d64b785c"}}
      >>>
      POST /session/0CEA7F27-EB9C-4FBF-97E3-481203F7D7AF/element/8493e4b2-ed09-4653-a005-2a07d64b785c/click HTTP/1.1
      accept: application/json; charset=utf-8
      {}
      <<<
      HTTP/1.1 200
      content-type: application/json;charset=UTF-8
      server: Microsoft-HTTPAPI/2.0
      access-control-allow-origin: *
      date: Wed, 08 Jun 2016 00:36:45 GMT
      connection: close
      content-length: 106
      {"sessionId":"0CEA7F27-EB9C-4FBF-97E3-481203F7D7AF","status":13,"value":{"message":"Element is obscured"}}
    • To add to the above, it appears the commenting tool has mangled the snippet. But you can see the relevant portion at the bottom.

    • I’m also experiencing the same problem. The workaround I’m using is to click with Javascript. E.g. -
      driver.executeScript("arguments[0].click()",elementThatIsntReallyObscured);

      This is obviously an imperfect solution because if the element really is obscured, the test won’t catch it. But until this bug is fixed, if you do the above when Edge is being used, it’s better than nothing.

    • Same here.
      On my test site, the button can actually be obscured by a div, but even after “clicking” it to make the obstruction disappear, it still give an exception

    • Facing a similar issue - populate a form and click on submit, it gives the following error

      16:44:15.240 INFO - Done: [find element: By.className: login-btn]
      16:44:15.261 INFO - Executing: [click: 2 [[EdgeDriver: MicrosoftEdge on ANY (362FA966-6361-405E-84AB-76A38A0829EA)] -> class name: login-btn]])
      16:44:15.638 WARN - Exception thrown
      org.openqa.selenium.WebDriverException: Element is obscured (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 18 milliseconds
      Build info: version: '3.0.0-beta1', revision: '8e4315c', time: '2016-07-28 18:04:05 -0700'
      System info: host: 'Lenovo-PC-RB', ip: '192.168.128.212', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_102'
      Driver info: org.openqa.selenium.edge.EdgeDriver
      Capabilities [{applicationCacheEnabled=true, acceptSslCerts=true, browserVersion=38.14393.0.0, platformVersion=10, locationContextEnabled=true, webStorageEnabled=true, browserName=MicrosoftEdge, takesScreenshot=true, pageLoadStrategy=normal, takesElementScreenshot=true, platformName=windows, platform=ANY}]
      Session ID: 362FA966-6361-405E-84AB-76A38A0829EA
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
              at java.lang.reflect.Constructor.newInstance(Unknown Source)
              at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
              at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
              at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:683)
              at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:319)
              at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:85)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
              at java.lang.reflect.Method.invoke(Unknown Source)
              at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement$1.invoke(EventFiringWebDriver.java:331)
              at com.sun.proxy.$Proxy4.click(Unknown Source)
              at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click(EventFiringWebDriver.java:344)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
              at java.lang.reflect.Method.invoke(Unknown Source)
              at org.openqa.selenium.remote.server.KnownElements$1.invoke(KnownElements.java:64)
              at com.sun.proxy.$Proxy5.click(Unknown Source)
              at org.openqa.selenium.remote.server.handler.ClickElement.call(ClickElement.java:30)
              at org.openqa.selenium.remote.server.handler.ClickElement.call(ClickElement.java:22)
              at java.util.concurrent.FutureTask.run(Unknown Source)
              at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
              at java.lang.Thread.run(Unknown Source)
      16:44:15.642 WARN - Exception: Element is obscured (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 18 milliseconds
      
    • As a workaround we can use JavaScript to click the element :
      Webelement element =
      driver.executeScript("arguments[0].click()", element);

    • Hi,
      I am facing the similar issue as when I am trying to click on a submit button via script it says "WebDriverException: Message: Element is obscured."But initially with the same selenium version and scripts it went through without any hurdles but again I checked out my files from the repo,it throws this error.

    • Hi,
      I am facing the similar issue as when I am trying to click on a submit button via script it says "WebDriverException: Message: Element is obscured."But initially with the same selenium version and scripts it went through without any hurdles but again I checked out my files from the repo,it throws this error.

      Test Environment
      Selenium version : 2.53.6
      OS build : 14393.187
      Webdriver version : 10.0.14393.0
      Platform : python binding

    • I wouldn’t hold my breath it’s been an issue for 6 months and MS hasn’t responded at all.

      It’s honestly exceptionally disappointing.

    • But why webdriver is showing up dynamic behavior,with the same version, I was able to click a day before but today I am not able to click on the same without any selenium update or any update except a new checkout for my files.

    • Dear Microsoft,

      Is it possible to get an estimate on when this issue can be fixed?

      Thank you.

    • Hi, same issue, any update please?
      Currently using JS workaround as above.

    • Same issue here with Edge. If I replace the EgdeWebDriver for InternetExplorerDriver the tests are working perfectly.

      So Edge is in this state untestable for me.

    • Same issue I experienced but i used below workaround it was working for me.
      driver.find_element_by_css_selector("[id=’id_name’]") --> this code not worked,
      driver.find_element_by_css_selector(“#id_name >div > span”) --> this is worked fine.
      I had to use end span to perform click , anyone please suggest why this method is working , why top level id not worked.

      Thanks and Regards,
      Gobi

    • Both projects have this bug with “submit” button. Cannot proceed. Using windows10, Edge and robot (Robot Framework 3.0 (Python 2.7.11 on win32). Serious issue.

    • I am also getting similar issue. Do any one know when we will be getting a solution for this ? Thanks.

      Failed: Element is obscured (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 16 milliseconds
      Build info: version: '2.52.0’, revision: '4c2593c’, time: ‘2016-02-11 19:06:42’

      Driver info: org.openqa.selenium.edge.EdgeDriver
      Capabilities [{acceptSslCerts=true, browserVersion=25.10586.672.0, platformVersion=10, browserName=MicrosoftEdge, takesScreenshot=true, pageLoadStrategy=normal, takesElementScreenshot=true, platformName=windows, platform=ANY}]

    • The same issue is showstopper for me.
      WebDriverError: Element is obscured (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 2 milliseconds
      Build info: version: '2.53.1’, revision: 'a36b8b1’, time: ‘2016-06-30 17:37:03’
      System info: host: 'wks-fin-devel’, ip: '172.17.59.88’, os.name: 'Windows 10’, os.arch: 'amd64’, os.version: '10.0’, java.version: ‘1.8.0_111’
      Driver info: org.openqa.selenium.edge.EdgeDriver
      Capabilities [{applicationCacheEnabled=true, acceptSslCerts=true, browserVersion=38.14393.0.0, platformVersion=10, locationContextEnabled=true, webStorageEnabled=true, browserName=MicrosoftEdge, takesScreenshot=true, pageLoadStrategy=normal, takesElementScreenshot=true, platformName=windows, platform=ANY}]
      Session ID: 59138523-C1B6-4876-A8DA-6DCB9053F624
      at WebDriverError (C:\MyApp\node_modules\selenium-webdriver\lib\error.js:26:26)
      at Object.checkLegacyResponse (C:\MyApp\node_modules\selenium-webdriver\lib\error.js:639:15)
      at parseHttpResponse (C:\MyApp\node_modules\selenium-webdriver\http\index.js:538:13)
      at C:\MyApp\node_modules\selenium-webdriver\http\index.js:472:11
      at ManagedPromise.invokeCallback_ (C:\MyApp\node_modules\selenium-webdriver\lib\promise.js:1379:14)
      at TaskQueue.execute_ (C:\MyApp\node_modules\selenium-webdriver\lib\promise.js:2913:14)
      at TaskQueue.executeNext_ (C:\MyApp\node_modules\selenium-webdriver\lib\promise.js:2896:21)
      at C:\MyApp\node_modules\selenium-webdriver\lib\promise.js:2820:25
      at C:\MyApp\node_modules\selenium-webdriver\lib\promise.js:639:7
      at process._tickCallback (node.js:401:9)
      From: Task: WebElement.click()

    • I am not able to interact with a webpage for simple item as mouse clicking links or emulating the enter key press event. Its hard pressed to believe that is not working … curious if anyone is able to interact with a page via mouse click / enter key of form elements… Dear Ben B from Microsoft would you please update us with ETA :)

    • I am also facing same issue as on clicking the visible button of search , I am getting the Obscure error. On edge and win10.

      driver.findElement(By.cssSelector(“button#_fZl”)).click();

    • I have the same issue in a simple test: Element is obscured. Used executor to workaround
      However I tested the same code in two pcs:

      • one with windows 10 home/amd A8 processor : test failed and cannot use button.click functionality. Also, ie11 webdriver failed.
        -other with wndows 10 Pro/ intel Core i7 5th generation: test worked perfectly.Also webdriver for ie11(with adminstrator rights in eclipse)
        I think the issue would be related to the windows 10 version or perhaps with the processor used.Microsoft would know more about it.
    • Hi All,

      Even I faced this issue and raised it here.Now I have workaround for this.

      Instead of direct clicking on the element we can move to that element and then click that element.

      Use action chains to move to that element and click ,it will work.Worked for me :)

      Python binding with selenium wayout:

      el = find_element_by_xpath(self.locator)
      ActionChains(driver).move_to_element(el).click().perform()

      #java
      Actions action = new Actions(driver);
      action.moveToElement(element).build().perform();

    • Microsoft Edge Team

      Changed Assigned To from “Ben B.” to “Stanley H.”

      Changed Steps to Reproduce

    • Hi , I am facing this issue (Element is obscured) for all the elements on the page ,from last two days. Before that the elements are detected with out any issue.
      Also I see this might be related one recent update in my laptop.
      I have recently(On 5/1/17) installed the updates
      1.Visual studio 2015 update3 (KB3022398)
      2.Update for Microsoft Windows (KB3150513)
      Is this issue has any relation with these updates as I am seeing the issue quite recently ,not before.
      Also as noted above. Work around works for me:
      Actions act = new Actions(driver.Instance);
      act.MoveToElement(profileButton).Click().Perform();
      But I don’t want to change all the code at this point of time and want to wait for few days to know on the rootcause of the issue, any possible fix and then as a last step will have to change in all places.
      Thanks.

      Thanks.

    • Microsoft Edge Team

      Changed Assigned To from “Stanley H.” to “Clay M.”

      Changed Assigned To from “Clay M.” to “Mustapha J.”

    • Dear Microsoft,

      Please can SOMEONE supply us with any kind of status update on this issue. I cannot find a single response from you anywhere regarding this matter, other than you guys passing the incident around your team like a hot potato!
      You’re leaving a lot of people in the dark here and as said above, this is literally a showstopper unless we re-write our entire test suite and replace every element click with the JS work around mentioned previously.

      Thanks in advance :)

    • Honestly Ben T you’re far better off giving up on Edge than trying to test with it. This defect was opened a year and half ago and Microsoft has done absolutely nothing.

      They haven’t even bothered commenting on it in a year in a half, that’s how little this show stopper means to them.

      I guess it’s to much to hope for that the edge team would be like the net core team and actually be responsive to users, let alone huge show stopper issues.

    • Hey Ben,

      We have multiple issues in this area (Element is Obscured). Our logic takes into account a lot of variables such as IsDisplayed, if it hit tests, and if it has a clickable point. In this exact case we’re failing to run a click on a <tr> when it has an even number of <td>’s. We are investigating this issue to fix this bug but if you’re having failures with Click() in other areas then you should file a bug with your setup (build of windows, build of webdriver, test code and test page) and we’ll take a look.

      I’ll also note a good workaround for the time being would be to use execute script and try clicking the element via JavaScipt. While this doesn’t take into account as many variables as we handle with our Click() (hit testing being one such thing) it tends to be a good workaround for these types of issues.

      Thanks,
      Clay

    • Microsoft Edge Team

      Changed Title from “Clicking Displayed Element Returning as Obscured” to “Clicking <tr> with even number of <td>'s returns "Element is Obscured"”

      Changed Assigned To to “Rick J.”

    • 8/6/2017
      Win 10 1703 OS Build 15063.483
      Microsoft Web Driver 10.0.15063.0
      Still failing on simple Google Home Page
      driver.findElement(webdriver.By.name(“btnK”))
      .then(function(btn){ btn.click(); } << ELEMENT IS OBSCURED

      Tragic, considering how many Selenium examples go to http://www.google.com, sendKeys to ‘q’ and click as your first test example.

    • Are there any plans to make edgedriver to able to click? Or it is extremely complicated?

    You need to sign in to your Microsoft account to add a comment.

    Sign in