With the latest version of chrome: Version 61.0.3163.79 (Official Build) (64-bit), as well as Chromium: Version 61.0.3163.100 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)
I have an issue where when creating a gwt-SuggestBoxPopup, the position coordinates being passed are incorrect.
I've tested this against all the other browsers, IE, Firefox and Safari, they all work there, even the older version of chrome (Version 60.0.3112.78) worked fine. I've also tested this on a Linux, Windows and Mac machines Nothing has changed on my end so I know for a fact something has changed on Chrome's end with the new update.
The only thing now is trying to figure out of this is a bug or a Chrome change, and if it is a chrome change, where that is documented.
This bug has been fixed in GWT version 2.8.2. Its release notes state that "Chrome 61 removed functionality that had been used for reading the absolute top/left values. The internal implementation has been updated to reflect modern standards.".
Related
For Android Version, less than 11 My app is working fine. But for the versions of Android 11, it shows a message " Please install Chrome Stable 72 or later" when I try to open the app.
Change dependency from
implementation 'com.github.GoogleChrome:custom-tabs-client:a0f7418972'
to
implementation 'com.google.androidbrowserhelper:androidbrowserhelper:2.2.0'
Also make sure Launcher activity in manifest imported from androidbrowserhelper
com.google.androidbrowserhelper.trusted.LauncherActivity
More migration details you can found here
Trusted Web Activity was introduced in Chrome version 72. The issue there is not related to the Android version, but that the version of Chrome installed on the devices showing this message is earlier than 72.
installing the latest version of Chrome from Google Play should solve the issue.
When I run the following command in my Chrome console the viewer gets black rectangles covering it (sometimes in a L-like shape). Apparently running it on any page with a viewer causes the error. This is causing errors with part of our product.
NOP_VIEWER.impl.setPostProcessParameter("style", "edging");
Viewer version: 6.5 - I was also able to replicate in 6.6.
Chrome Version: Version 75.0.3770.80 (Official Build) (64-bit)
Seems to work in older versions of Chrome
We've fixed this and pushed a patch to production. Please try again in version 6.6.4.
I am using Chrome Mobile Web Emulation.
Issue:
After updating chrome and chromedriver, click functionality is stopped working.
Stack-trace:
Not available, no exception or error is thrown.
Chrome version: Version 67.0.3396.62 (Official Build).
ChromeDriver: Version 2.39
Selenium: Version 3.12.0
Issue resolved after updating Chromedriver to 2.40.
They provide a version upgrade patch 2.40, just 7 day after releasing 2.39 version.
My Chrome automatically updated itself to Version 46.0.2490.71 (64-bit) today 10/14/15, and it looks like the developer tool is broken – it can not be launched.
I uninstalled Chrome latest, and installed Version 45, the developer tool is working fine. But then Chrome immediately upgrades itself to Version 46 again.
I tried to stop the auto upgrade of Chrome by: defaults write com.google.Keystone.Agent checkInterval 0
that does not seem to have any effect – Chrome still tried to auto-upgrade itself.
Is there anyone else using Chrome latest and have the same issue?
I am trying to run tests in Chrome browser 32.0.1700.76 (latest) using Selenium 2 Webdriver with chromedriver version 2.4
Chrome starts but the string "data;" is displayed in the url bar.
Those test worked fine with a previous Chrome version (28.xxxxx) but I can't downgrade Chrome.
Can anyone suggest me how can I solve the problem?
You need to either upgrade the ChromeDriver you are using or find a way to downgrade Chrome.
The basic principle of the issue is that the ChromeDriver v2.4's support of the most recent versions of Chrome is non-existent.
You get similar issues with Firefox, an upgrade will sometimes break the tests.