D
D
Dmitry2013-08-06 16:10:14
ASP.NET
Dmitry, 2013-08-06 16:10:14

Selenium Webdriver + ChromeDriver - bugs in working with Russian letters?

We encountered a strange bug when running functional tests based on Selenium WebDriver - some Russian letters do not reach the browser.

Code example:

var Browser = new ChromeDriver("../../");
Browser.Navigate().GoToUrl("/form/");
Browser.FindElement(By.Id("fio")).SendKeys("Иванов Иван Иванович");


But in the browser, in the input field, the string " new vn new " comes.

Website in UTF-8, source code in UTF-8.
Chrome latest version - 28.01.1500.95m Chrome
driver is also the latest - v2.1.210652
Environment: Windows Server 2008 R2, Russian interface.

Clarification - on some computers there is no stable bug , on some - there is stable .

Answer the question

In order to leave comments, you need to log in

4 answer(s)
Y
Yaroslav Astafiev, 2013-08-20
@Newbilius

Well actually here. The comments say that everything is fine in Firefox.
You can use an older version of the driver. Well, or already proposed js \ jQuery
You do not see "And", "a". In general, the problem is not on your side.

D
Dmitry, 2013-08-07
@Newbilius

It is a pity that the minuses are anonymous - so there would be an opportunity to ask the person who set what I missed for the obvious thing.

H
humblegenius, 2013-08-07
@humblegenius

This is most likely due to the fact that selenium tries to emulate pressing each button and not all keys are able to premise. I solved similar glitches in the IE driver by disabling native browser control (“EnableNativeEvents = false”):

new OpenQA.Selenium.IE.InternetExplorerDriver(
    new OpenQA.Selenium.IE.InternetExplorerOptions {
        IntroduceInstabilityByIgnoringProtectedModeSettings = true,
        EnableNativeEvents = false
    }
)

See if there is a similar option for Chrome too.

A
AxisPod, 2013-08-07
@AxisPod

I didn’t use these libraries myself, but the first thing to do is to take dotPeek for example and dig into the outcomes of these libraries. Again, there is a feeling that the jamb with encodings is related to the fact that the native encoding for Windows is still UTF-16 (UCS-2).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question