I'm having an issue with a random set of users running Windows 10 and IE11. When the issue occurs the user are in an IE 11 browser session and will see among other things that selected div sections will scroll text but the textboxes and dropdowns will remain static within that div.
The current fix is to start a new browser session not just a new window. Currently this only occurring in about 15-20 out of 700 users. Pages are running with doc mode Edge and user agent default.
I realize this is a rather sparse explanation but that is what I have so far. Does anyone have a suggestion as to what could be causing the issue or a tool that would allow further investigation into the browser session?
From your description, I assume that this issue is not related with website and issue is with IE browser.
I suggest you to check for latest Windows and IE related updates. If any new updates are available than try to install new updates and again check for the issue.
If no any new updates available than try to reset the Internet Explorer browser to check whether it fix the issue or not.
If issue persist than you can try to unchecked the Internet Explorer option from Turn Windows features on or off and again try to check that option to add the IE again.
Let us know about your testing results. If issue persist than we can try to provide further suggestions.
Does anyone happen to know why the pagingTextBox doesn't work when using the dgrid pagination? It works fine in FireFox and Chrome but when hitting the enter key in the textbox in IE, it does nothing. I'm using IE 10, but also tried with IE 8. I need this functionality in all 3 browsers. Thanks.
The only event that the paging textbox listens for is change. Apparently, pressing enter registers this event on Chrome and Firefox but not IE. I'm not sure what the reasoning is behind that.
This seems like a legitimate issue to report on dgrid's GitHub issues page though. It shouldn't take too much effort to fix, even if it means listening for 2 types of events.
I created the following jsbin to show the problem. http://jsbin.com/fewuli/2/ If you run this in any browser but IE10 and focus the input then the box shadow outline looks great like this:
But if you run this in IE10 (or IE9+) it doesnt render the top portion of the box shadow on focus like this:
Is there any way to fix this without increasing the box shadow size (last option?)
I tested the link you provided and checked it out in different versions of IE (11, 10 and 9) and they all showed the input box being highlighted when it held the focus. (I used the IE toolbar Emulation to view the differences)
If you are still having problems with this you could try adding a script that helps older IE browsers support HTML5. Modernizr is one of these scripts that will help in this way. There is also HTML5 Shiv but that only supports IE browsers 9 and older.
Another suggestion would be to try MS Visual Filters and Transitions and apply it to your INPUT class:
filter: progid:DXImageTransform.Microsoft.Blur(PixelRadius=3,MakeShadow=true,ShadowOpacity=0.30);
-ms-filter: "progid:DXImageTransform.Microsoft.Blur(PixelRadius=3,MakeShadow=true,ShadowOpacity=0.30)";
I have read the advice on posting a question that should be as precise as possible and used the advanced search facility so I hope my question has not been covered previously.
NOTE: I am not a programmer and can only just about find my way around code (in my site`s cpanel).
My site`s login popup box does not work in Firefox - although it did so for 3 years prior, up until a few weeks ago, so maybe there is an issue with a recent FF update). It does however work OK in Chrome.
Hovering over the login/register text shows the alt tag "Click to show popup login form" but nothing happens when clicked.
Can you provide a URL for others to see what you're referring to?
Firefox was just updated to version 18 I believe. I would try and downgrade to 17 just to confirm that it's an issue with FF. If it is I'd open an issue with mozilla (https://bugzilla.mozilla.org/). Also search there for your issue.
I am using Selenium WebDriver 2.5.0 (tried 2.13.0, it did not help).
I am trying to click on a link like this:
driver.FindElement(By.PartialLinkText("Customer - Creation").Click();
Before it worked, but I have tried to run the scripts after 3 weeks and
I observe 3 different behaviors on 3 machines:
Machine A: There is no click on the link at all, also there is no error.
Machine B: It clicks a different link! Sometimes one above, sometimes one below.
Machine C (Virtual): It works.
I have not fully tested this (spent half a day today), but did anyone stumble upon such a behaviour?
I have restarted my PC, re-added the Selenium libraries.
"SendKeys(Enter)" helps, but this issue happened not only to links, but to at least radio boxes as well, where "SendKeys(Enter)" does not work.
Please share your thoughts.
Update: Browsers are the same on at least 2 machines, Internet Explorer 8.0
Answered by nebehr.g...#gmail.com at Selenium Issues:
This issue keeps popping up from time to time and is usually returned with request for clarifications. The bottom line is, InternetExplorerDriver calculates coordinates of some objects incorrectly and clicks in the wrong place. One reason for this is zoom value other than 100%; however it is reproducible for some controls for 100% zoom as well.
I suppose it would be helpful if you could create a sample page to demonstrate this issue. In the meantime why don't you use Javascript click() method for offending controls?
http://code.google.com/p/selenium/issues/detail?id=3052
One other thing to check for is the screen resolution (not the desktop resolution but the system level size of text and icons). I have two laptops in my office that are you used for testing, one running Windows 7 and the other running Windows 10. On both, the screen resolution was greater than 100% and Selenium was having problems moving the mouse to the correct location for mouse events like click and hover. As soon as the screen resolution was set to 100%, all mouse actions worked correctly.
Windows 7: http://windows.microsoft.com/en-us/windows7/make-the-text-on-your-screen-larger-or-smaller?v=t
Windows 10: https://superuser.com/questions/951199/windows-10-system-font-size-change
There is a lot of useful info in Andrey's answer and in the Selenium issue he mentions at https://code.google.com/p/selenium/issues/detail?id=3052. Just to tie all those pieces of info together and offer a successful workaround...
I too am experiencing the issue of clicks occurring at the wrong screen coordinates -- four years after the OP first mentioned it! As others have said:
The issue is related to InternetExplorerDriver. I have the problem
when testing IE 9, but not Chrome, Firefox or even IE 8.
As mentioned in the Selenium issue, the website I'm testing uses frames.
I tried several workarounds suggested in this post and elsewhere. All of the following did NOT help:
Updating to the latest InternetExplorerDriver (version 2.47.0)
Maximizing the browser window.
Setting browser zoom to 100%.
Using an action chain, with or without move_by_offset, instead of WebDriver's click() method.
As suggested by Andrey, what DID help is using JavaScript instead of WebDriver's click() method. Here's a line of Python code that does the trick:
driver.execute_script("jQuery('{}').click();".format(css_selector))
This assumes that "driver" is an instance of Selenium WebDriver, and "css_selector" is a string identifying the element you want to click, and that jQuery is loaded.
Sounds like the element isn't present in the page's HTML, but is instead added dynamically once the page is loaded. What happens depends on how fast the machine is and how unique the text is. I'll bet that if you added a long sleep (e.g., a minute) you'd get the same result on all 3 machines. If so, that indicates the single most classic Selenium testing problem - trying to act on pages that aren't complete. You need to find an element to wait on that will guarantee the presence of the link you'd like to click on.
I just had the same issue in FireFox. The zoom was at 100% and the selection was by xpath an certainly correct. Turned out the problem disappeared when I maximized the browerwindow!
code :(python api)
self.driver.maximize_window()