I would like to known if the webNavigation API is still experimental, because I need to use chrome.experimental.webNavigation.onBeforeNavigate.addListener in a chrome extension. So far I found http://code.google.com/chrome/extensions/trunk/webNavigation.html and http://code.google.com/chrome/extensions/experimental.webNavigation.html - which one is valid?
webNavigation went stable in Chrome 16, which just landed minutes ago! http://code.google.com/chrome/extensions/webNavigation.html
The webNavigation API is still experimental. The first link has /trunk/ in it which referes to the prerelease documentation matching Chrome Canary or Chromium. You can read more about the documentation versions here. It looks like Chrome 17 is the planned milestone for webNavigation but that could get pushed back.
Related
By some project reasons I have to use Selenium 4 (4.0.0-rc3) and Chrome version 71.
Of course the current chromedriver (version 94) doesn't work with old chrome.
I have downloaded the source code of chromium project for debugging and try to understand how actually driver works with selenium. Probably I will try to make my own driver version but at this moment it seems like an inefficient solution.
I am really stuck with this and will be happy to get any advice.
Is it possible just to configure driver by capabilities (or any parameters) for working with old chrome?
The Chrome version you're targeting Chrome 71 is already deprecated. Using Selenium 4 with this much obsolete version of Chrome will not work and I think apart from creating your own code piece, there is nothing much you can do.
Using such an obsolete piece of software, in this age of internet, will open a pot of bugs for you, and if you use this to connect to internet, then chances are people may exploit any hidden security vulnerabilities to attack your application.
I would strongly suggest you to talk within your project team to use an updated version of Chrome.
ChromeDriver 2.46 will work with Chrome 71.
We have an internal Windows server with OpenFire 4.5.1 with inVerse 6.0.1 Release 1 installed. The plugin works great from Chrome browser and Edge browser, but I really need it to also work from IE11, if possible. When initial page loads, there are 2 errors:
IE11 console image
If you can't see the image: 1. Syntax error converse.min.js (55,35487) 2. 'converse' is undefined inverse (43,17).
Looks like a show-stopper. Not sure how or if a fix is available.
Thanks!
From the Converse Github issue, we can see that there have many threads about Converse plugin not support IE browser. Such as: Support for IE 11 and iOS Safari 9.3
According to these issues, we can know that Converse uses quite a few features not supported by IE11, not just arrow functions. So, perhaps this plugin doesn't support IE browser or it needs to install some Polyfill. You could contact Converse developer team and ask them whether there have a workaround, or feedback this issue to Converse Issue forum.
I tried navigating to the Chrome driver website and saw that the latest release being documented was 2.22, but when I got to the index page, I saw that 2.9 was mentioned down the hierarchy.
Can somebody please help in understanding the above?
Please find chrome driver here
https://sites.google.com/a/chromium.org/chromedriver/downloads
The versions on the chromedriver download page are sorted alphabetically, not numerically or chronologically. That means that 2.9 appears at the bottom of the page, which might make it look like the "last" or "most recent" version. The actual most recent version as of this writing is, in fact, 2.22.
Use this Selenium site you have drivers for all browsers even for phone's.. Check it
http://www.seleniumhq.org/download/ - You may find there chrome webdriver 2.22Version
I heard Google is having plans to support ORTC standards from version 38 or 39, but haven't seen any confirmation on it.
https://bloggeek.me/google-roadmap-webrtc/
This was on the roadmap but did not happen.
Programmatically , you can check for the existence of the RTCRtpSender object. It's not there in the canary version (43 as of today) of chrome even.
I like to use the most up to date version of Chromium, Google's open-source version of Chrome. The problem I have about Chromium is that the userstring can always uniquely identify my system based on the version number (as not too many people keep up to date with the Chromium snapshots).
My question: is there a way to modify Chromium to always send out a DEFAULT user string agent (i.e. Chrome version 29 or Firefox 24, not Chrome 32)? Thanks for any help!
I think there is a command line option for that, e.g.
chromium-browser --user-agent="Chrome version 29"
For more details see this page: Chromium tips and tweaks.
(Note: I'm not sure if it will work in future versions)