In my current automation framework that uses Serenity we recently updated our version of ChromeDriver from version 2.36.54047 to 89.0.4389.23
In the previous version when an alert showed up it was accepted and the automation ran without issue. When I switch back to the new version 89 of chromedriver, the alert shows up and then disappears within a fraction of a second. The test then fails because the alert was not seen by selenium.
Does anyone by any chance know why this would be happening?
In serenity the code looks like:
as(actor).getAlert().accept();
Related
I am using Chrome to debug an app. Usualy I get a complete stacktrace when profiling my app.
But recently the stack just disappeared. It only shows the layering, drawing and native events, but no longer the JavaScript executions.
In the settings I have uncheckt the "Disable JavaScript samples" and tested all other preferences regarding the performance tab. Nothing helped.
Other sites (like stackoverflow) won't work eighther. Chromium has the same problem.
I am running this on Ubuntu 18.04.4 LTS.
Anyone else has a clue how to fix this?
I'm affected by this as well. I filed an issue at https://bugs.chromium.org/p/chromium/issues/detail?id=1071961. Perhaps you could add more detail so the Chrome team can fix it faster.
Are you using an Intel CPU or an AMD one? I'm using one of the latest AMD Threadrippers. Wondering if that may be the cause.
I am making a Chrome Web Store application. My app was on version 1.5 and recently I updated it to version 1.6 and then to version 1.7
For some reason the Developer dashboard is telling me that the public version is 1.5 and the draft version is 1.7, and I don't know how to make my app 1.7.
What should I do?
From the Dashboard item's Edit page, you press "Publish changes".
And then.. You wait. Do not cancel a publish in progress.
Chrome Web Store runs heuristics on your app to check it for malicious or dangerous code. Usually this takes up to an hour before your version goes public.
Sometimes an extension/app is flagged for manual review. Then it can take longer, but there's no way to tell how long.
As long as your Dashboard says "Publishing in progress", you just have to wait. If it is in this state for too long, you can try contacting Web Store support.
I've picked up the discover meteor ebook earlier today and have been following the steps. It's been a great experience and I hope I can contribute to this community once I have a more thorough understanding of the technology. All is going well and I was using firefox as my browser. I decided to install chrome since that is the browser I use on my host machine on a day to day basis. However when I load the project up in chrome its a blank screen. The console reports the following(pastebin)
http://pastebin.com/wvEaVNPv
Has anyone else experienced this issue?
YES! It comes and goes with time or development, and you will get different results in different browsers (ubuntu). I currently am getting
Uncaught ReferenceError: Package is not defined meteor.js:21
Uncaught ReferenceError: Package is not defined standard-app-packages.js:21
Uncaught ReferenceError: Package is not defined random.js:21
etc
A few weeks ago, chrome canary was bad but release chrome not. It may be some subtle code issue triggers things because as I developed madly but checked intermittently that problem came and went maybe three times, and once another browser gave me a clue on something it didn't like, which also cured chrome.
I don't have any tools/concepts to debug this further. I initially got through Discover Meteor using chrome about 2 months ago.
Check your accounts-ui-bootstrap-dropdown. If you are using bootstrap-3 you'll need accounts-ui-bootstrap-3. I found this as one possible cause when I went back.
Is this possible? I think I may have missed something obvious here. I have a live UI scripts app, and I need to fix a bug. The potential bugfix has to be tested on multiple browsers, so it actually has to be published, instead of just trying out the "current version". This means that it has to be published to a new URL.
Thanks.
it actually has to be published, instead of just trying out the "current version" ?
There is no reason why using different browsers should prevent from using de 'dev' version of an app... you can login in many browser at the same time and play with the dev version on each browser (I do that very often using a couple of android and osX browsers simultaneously). Did you try and did you meet issues doing so ?
I need to check a bug in Google Chrome for specific version like 14.0.802.30. How can I get the pervious version for that? Also, how can I switch off automatic update functionailty of Chrome?
Some old Chrome-Versions can be found on oldapps.com if you can't find the version there, you can maybe use the corresponding Chromium release? Its basically Chrome minus the Google-Spyware. For Operating Systems other than linux you have to build your own version tough (easy to follow instructions are published on the website).
Chromium-Releases can be found here