After the latest Chrome browser update (54.0), I am unable to invoke BrowserWindow.Launch() properly through ChromeDriver.
Issue being experienced:
Multiple window is are being opened, but there is no control on new window created.
A null pointer exception is throwing on windowHandle.
Resolution tried:
New ChromeDriver 2.25 updated
Latest CodeUITestCrossbrowsersetup installed
Please suggest if any more update need to be done or alternative ways to solve this issue.
Thanks in advance.
Related
Web Automation using Test complete tool.
Unable view browsers such as firefox, edge as Browser(edge), it is displayed as Process(edge).
Tried links provided in test complete documentation regarding preparing browsers for web automation, doesn't seem to work. If anyone has faced this kind of issue and got it resolved please help.
Test complete version 14.4.
Firefox version : 77
Edge version: 83.0.478.58
To support a specific version of Firefox, you need to install the corresponding support modules. You can find these modules here:
https://support.smartbear.com/downloads/testcomplete/firefox-patches/
The "new" Edge based on Chromium isn't supported by TestComplete at the moment (2020-07-05), wait for an update from SmartBear. It should be released soon.
I'm using the webdrivermanager(Java) and I think is configured (pom.xml), because Chrome and IE are working. Only FireFox is showing this menssage "No configuration setting found for key 'wdm.geckoDriverVersion'"
*The exemple works to.
So, Boni or other member can help me with this problem?
Thanks.
EDIT:
I have this error only with PhantomJs and FireFox. The code is the same(examples git). First I thought that would be the POM but Chrome and IE are working. Thanks for your support.
https://i.stack.imgur.com/KJOnO.png
https://i.stack.imgur.com/at3qm.png
It seems that the library used by WebDriverManager for configuration (com.typesafe.config) is not able to find the properties file for some reason. As of WebDriverManager 1.5.0, this file name is webdrivermanager.properties.
In any case, I would use the latest version of WebDriverManager and try again.
I am having issue with value picker of extension library. When i use java file exitlib/pickers/SimplePicker.java system shows following errors.
i) SampleDataUtil cannot be resolved
ii) The import exitlib.SampleDataUtil cannot be resolved
I have gone through a thread on internet that in application properties advanced tab i have to check following 2 options
com.ibm.xsp.extlib.library
com.ibm.xsp.extlibx.library
but these options are not available to me. Can anybody guide me where I am having issue in implementing extension library.
Thanks in advance
It sounds like things are possibly not installed correctly....
Try tell http osgi ss com.ibm.xsp.extlibx on the server console to see if it is resolved.
If not, the installation hasn't worked correctly on the server.
Another option is you haven't installed in designer?
The below is a good reference for installing on both server and client
http://www.tlcc.com/admin/tlccsite.nsf/pages/extension-lib
Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.
I am using the chrome.runtime.port to connect to the background script. But for some users somehow the portId_ is missing from the port object. The weird thing is that its missing from some users not all. Any help would be appreciated.!
It looks like that they took out portId_ in chrome version 34. So some users are using the latest version of chrome and the others don't, but they are going to face the problem as soon as they update to the latest one.