-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IEdriver when i am typing some text in text field every single characters enters twice #5103
Comments
I experience the same issue with following setup: Looks like adding capability RequireWindowFocus = true solves the issue. |
Below I'll write options which allow to avoid this bug: |
Issue still exists if nativeEvents are turned off. This is simple reproducible script which demonstrates problem:
Script is tested with IEDriverServer 3.7.0. and Selenium 3.8.0. |
I am not able to reproduce the issue with IEDriverServer 3.8.0. and Selenium 3.8.1 anymore (nativeEvents are turned off). Although, typing is very slow now: every character takes about 5 seconds to be entered. |
@snatalia34 That’s an indication that you’re still using native events, and moreover, you’re using the 64-bit version of the IE driver. |
@jimevans IE driver 3.7 64bit + grid 3.7: each character entered twice |
It works with IE driver 3.8 32bit + grid 3.8.1 configuration because native events are turned on. |
This should be fixed in e0b5478, released as part of 3.10. |
The "fix" now causes IE driver to crash when native events are off. |
@dnkilka, have you tried 3.11? The crash should be fixed in that release. |
@jimevans, crashing issue still exists in 3.12.0 |
@Ishmael9947 I’m perfectly willing to believe a crashing issue exists in 3.12. I don’t believe it to be this crashing issue. You’ll need to supply some WebDriver code that exhibits your particular crash. Also, please be aware that I have no access to a laptop to investigate the issue for the next few days. I’m strictly limited to mobile devices until I’m able to get home. |
No problem - thanks! Windows 7 Pro SP1 Code is as follows:
Stack trace: Note: it doesn't matter whether the driver capabilities are set to true or false or not set - I get the crash no matter what. |
@Ishmael9947 The error you describe is entirely unrelated to the issue described in this issue report. Moreover, please don’t use the |
Inadvertently reopened this issue due to commenting on it using a mobile device from my hospital room. Reclosing. |
OS:
Windows 10
Selenium Version:
3.7.0, IDE - visual studio, programming language - c#
Browser:
Internet Explorer 11
Browser Version:
11.726.15063.0 (64-bit)
Expected Behavior - when I type some text (for example: "some text") it should be entered exactly as it was in code ("some text").
Actual Behavior - when I type some text (for example: "some text") every single charachter from it enters twice, (so result is like this "ssoommee tteexxtt").
Steps to reproduce -
here is the code (c#) which shall reproduce it:
using NUnit.Framework;
using Autotests.Selenium.TestModel.PageDeclarations.Inbox;
using System.Threading;
using Selenium.Core.WebDriver;
using System;
using Autotests.Selenium.TestModel;
using OpenQA.Selenium;
using OpenQA.Selenium.IE;
[Test]
public void TestTypingTextByIE()
{
var service = InternetExplorerDriverService.CreateDefaultService();
var IeOptions = new InternetExplorerOptions();
IeOptions.PageLoadStrategy = PageLoadStrategy.None;
IeOptions.IntroduceInstabilityByIgnoringProtectedModeSettings = true;
IeOptions.EnablePersistentHover = true;
IeOptions.EnableNativeEvents = false;
IeOptions.EnsureCleanSession = true;
IeOptions.RequireWindowFocus = true;
IeOptions.IgnoreZoomLevel = true;
IeOptions.FileUploadDialogTimeout = new TimeSpan(0, 0, 30);
var driverIe = new InternetExplorerDriver(service, IeOptions);
driverIe.Manage().Window.Maximize();
driverIe.Navigate().GoToUrl("https://devform.socialboards.com/demo");
Thread.Sleep(10000);
driverIe.FindElement(By.XPath("//textarea[@name='message']")).SendKeys("123412341234");
}
);
But as I could understand, the whole problem is in this option "EnableNativeEvents = false"
The text was updated successfully, but these errors were encountered: