Last modified: 2014-10-20 07:54:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61801, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59801 - Selenium bug for IE10 causes test failures for Flow
Selenium bug for IE10 causes test failures for Flow
Status: PATCH_TO_REVIEW
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-07 23:10 UTC by Chris McMahon
Modified: 2014-10-20 07:54 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2014-01-07 23:10:26 UTC
We need to file an upstream bug for Selenium and IE10. Here's the conversation I had with Jim Evans on #selenium: 



(03:48:24 PM) chrismcmahon: jimevans: I think you have something to do with Se and IE, yes?  Where would be the best place to report a bug?  I have an element that is invisible to FF and Chrome (and humans) but IE10 at least thinks it is visible.  
(03:49:12 PM) chrismcmahon: jimevans: IE10 in Selenium I mean, the element appears invisible to humans in IE10 also, just Selenium thinks it is visible. 
(03:49:55 PM) jimevans: :newissue
(03:49:55 PM) selbot2____: https://code.google.com/p/selenium/issues/entry
(03:50:24 PM) jimevans: but for the report to be actionable, you'll need to provide a page that repros the problem (or url to the same)
(03:50:47 PM) jimevans: if you won't provide the html to run against, the report is worthless.
(03:50:58 PM) chrismcmahon: thanks jimevans yeah, it's all in a public test env with public tests failing
(03:51:04 PM) jimevans: (and yes, i meant "won't", not "can't")
(03:52:08 PM) jimevans: don't expect me to look at it for a couple of weeks at least. i'm totally swamped with other stuff.
(03:53:46 PM) chrismcmahon: jimevans:  what I don't have at the tip of my fingers is a super-short demo of the problem, just test results in the context of a Jenkins build running Cucumber tests against Sauce VMs.   That's all public though, and easy to point to, if it would be adequate. 
(03:55:22 PM) jimevans: try to distill it down if you can. you have an element that you think doesn't do visibility correctly. make the page directly navigable to, and give a very simple script (doesn't matter the language) using the raw webdriver api
(04:01:11 PM) chrismcmahon: jimevans: I'll work one up.  If you want a quick look, hover on the blue "Selenium user" on this page to see text appear "Talk|contribs".  FF and Chrome rightly think "Talk|contribs" is not visible until after hovering, IE10 thinks they are always visible.  http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA
Comment 1 Gerrit Notification Bot 2014-01-09 15:54:17 UTC
Change 106522 had a related patch set uploaded by Cmcmahon:
demo script for Bug 59801

https://gerrit.wikimedia.org/r/106522
Comment 2 Chris McMahon 2014-01-13 14:54:31 UTC
The Selenium team reports this is now fixed.  https://code.google.com/p/selenium/issues/detail?id=6827&can=1&q=cmcmahon&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary

Next is to validate the fix and encourage Sauce Labs to update IEDriver
Comment 3 Gerrit Notification Bot 2014-01-23 17:48:02 UTC
Change 106522 abandoned by Cmcmahon:
demo script for Bug 59801

Reason:
Issue demonstrated by this code was closed upstream https://code.google.com/p/selenium/issues/detail?id=6827

https://gerrit.wikimedia.org/r/106522
Comment 4 Željko Filipin 2014-10-20 07:54:01 UTC
Is this resolved?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links