Last modified: 2014-09-01 16:49:46 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 T71399, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69399 - Chrome not populating text fields correctly
Chrome not populating text fields correctly
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Željko Filipin
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-11 14:27 UTC by Željko Filipin
Modified: 2014-09-01 16:49 UTC (History)
8 users (show)

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


Attachments

Description Željko Filipin 2014-08-11 14:27:09 UTC
Reported by S Page at QA mailing list[1]. Reported to Sauce Labs support[2].

1: http://lists.wikimedia.org/pipermail/qa/2014-August/001843.html
2: http://lists.wikimedia.org/pipermail/qa/2014-August/001846.html
Comment 1 Željko Filipin 2014-08-11 14:35:24 UTC
Sauce Labs support answer:

Allison Wilbur (Sauce Labs Help Desk)
Aug 09 02:03 AM

Hi there,

I'm sorry this issue suddenly popped up for you! Sauce Labs just recently updated the default versions of Chrome, ChromeDriver, and Selenium that we serve up when no version is explicitly requested in the Desired Capabilities we receive.

Previously, the default values were:

Selenium: 2.30.0
Chrome: 27/28 (depending on environment - 28 for Linux)
ChromeDriver: 26.0.1383.0

The new default values are:
Selenium: 2.40.0
Chrome: 35
ChromeDriver: 2.10

If you set your Desired Capabilities to the previous values, I suspect your tests will behave as they used to. For example:

desired_capabilities['selenium-version'] = '2.30.0'
desired_capabilities['browserName'] = 'chrome'
desired_capabilities['version'] = '28'
desired_capabilities['chromedriver-version'] = '26.0.1383.0'

The extremely odd behavior you saw with the recent versions update is something I'm currently investigating, and I've filed an internal ticket to get this problem fixed. It seems to be related to the later versions of Chrome/ChromeDriver for some reason, and specific to Linux. I found this issue with send_keys on the ChromeDriver forums: https://code.google.com/p/chromedriver/issues/detail?id=467 It's not quite the same issue, but it looks like there's some strange behavior with text input in Linux.

I hope the previous values perform well for you as a workaround while we investigate the issues with the more recent versions of Chrome. I've linked this ticket to the issue, so I'll be sure to let you know when the fix is out so that you can test on more recent versions. If you want to try the later versions, I've had some success looping through my input and sending one key at a time, so perhaps something like that would help out.

Sorry again for the trouble here. Let me know if you have any additional questions and I'll be happy to help. Hope you have a great weekend!

Best,
Allison
Comment 2 Gerrit Notification Bot 2014-08-11 14:54:17 UTC
Change 153408 had a related patch set uploaded by Zfilipin:
Chrome 28 is the last version that works properly on Sauce Labs

https://gerrit.wikimedia.org/r/153408
Comment 4 Gerrit Notification Bot 2014-08-13 08:13:41 UTC
Change 153408 merged by jenkins-bot:
Chrome 28 is the last version that works properly on Sauce Labs

https://gerrit.wikimedia.org/r/153408

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


Navigation
Links