I am using two different third party programs (different companies) that apparently use the Google Maps Javascript API. When they load the map, the world map is shown, but an Error message is displayed: "Der von Ihnen verwendete Browser wird von Google Maps Javascript API nicht unterstützt. Verwenden Sie einen anderen Browser". (Translation: The browser you are using is not supported by Google Maps Javascript API. Use another browser). I am using Windows 7 and Internet Explorer 11.0.48. Early 2017 the programs were working correctly. I changed the default browser to Chrome using the option provided by chrome, but the error still appears.
Is there a workaround on the user side?
Regards
Peter
One of the programs is downloadable from http://www.codres.de/google-map-saver (GMS.NET), the other one came with a GPS logger from Canmore GPS on CD ROM and dates from 2013.
Both show the same behaviour, GMS.NET after clicking the button "Go to location", GPS Photo Tagger right after start up. The english error message is "You are using a browser that is not supported by the Google Maps JavaScript API. Consider changing your browser. Learn More, Dismiss". When I click "Learn more" I am told that IE 11 is my current browser. When I click an internet link in an e-mail Google Chrome is used (as default browser). It seems to me that the JavaScript API does not recognise Chrome as the default browser. IE11 is not run in compatibility mode. The Notebook I am using runs Windows 7 64bits.
I clicked the link in geocodezip's response. This sample works correctly calling Chrome (even when I copy the code into MS Word). When I open the link in IE11 it also works correctly. Is it possible to define the InternetExplorer as default browser in the Javascript API? This might be the reason for the different behaviour of the geocodezip sample and my programs. In this case the programs would have to be mended.
It seems a number of programs show this error since late 2017. The underlying problem here seems to be that they are all using an embedded webbrowser relying on IE technology. This embedded webbrowser needs to signal the proper IE version to the Google Maps JS library. Unfortunately, only the programmers of that software can do this. Adding the following to the page's source usually helps:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Look here
https://developers.google.com/maps/documentation/javascript/versions
<script async defer src="https://maps.googleapis.com/maps/api/js?v=3.31&key=YOUR_API_KEY&callback=initMap">
see v=3.31
latest is now 3.32 and if is not specified it will use the latest
And here
https://console.developers.google.com/apis/credentials/key/
check all api restrictions
I had the same issue with users on Windows 7 IE and no Chrome browser installed.
Added the following line :
<meta http-equiv="X-UA-Compatible" content="IE=11" />
Which seems to have resolved.
It seems that Google has dropped support for legacy systems (like Windows 7, earlier versions of IE) in Javascript API even with v3. It was working until this month, and what i also noticed that adding "v=3" string to maps api URL is no longer helping IE clients to run it without error. It's not a good behaviour of Google that there are older clients using v3 api with older IE verions which were working perfectly until this month.
Related
I am working on a web site that is served via a Mikrotik Router.
It's a site to provision internet for users up to 100m away.
When you connect to our Wifi, a sign in page is supposed to pop up where you enter your credentials to authenticate and use our internet.
For some weird reasons whenever the user tries to sign in, for android users the Android OS keeps on presenting their default browser to sign in on the Network. Unfortunately, it appears that the Javascript is not running on the native default Browser that popped.
I am not using any ES6+ features so I'm currently lost at what could be wrong.
When I previewed the Site on Google Chrome/Opera Mini and Phoenix Browser, the javascript is working very well.
I added this tag before the closing tag of my head element:
<noscript>
<div>
We're sorry but our site <strong>requires</strong> JavaScript to work.We recommend you use Google Chrome.
</div>
</noscript>
to be displayed if Javascript is disabled, but it is not even displaying.
I tried inspecting with Google Chrome devices inspection but it seems Google Chrome devices inspection only works with Google Chrome Mobile Browser(I might be wrong).
Any insight to fix this would be really appreciated.
Thank you.
I think you need to set setDomStorageEnabled(true)
for the webview settings.
You can read more about webview here:
http://tutorials.jenkov.com/android/android-web-apps-using-android-webview.html
As far as I know, in browser, such as Chrome, sharing desktop or application needs a Chrome Extension to work, eg:
chrome.permissions.request({
permissions: ['desktopCapture'],
}
But why does Google Hangouts do not need any extension to capture desktop?
Is there any API of JavaScript for this?
As of now, Google Hangouts does use an extension, it's just integrated into Chrome to the point of not being visible.
Source: Chromium issue to remove this special treatment
You can test that it is (stealthily) installed by manually opening
chrome-extension://nkeimhogjdpnpccoofpliimaahmaaome/background.html
At the same time, work is ongoing to support WebRTC spec for screen sharing (getDisplayMedia) in Chrome. It's not yet enabled by default in released Chrome versions, but will be very soon (code is already in the codebase).
Implementation tracking: Chromium issue
I've started fiddling around with U2F and it's looking really promising. Got myself some security keys and started digging into it.
I've managed to create a working register/login demo website which works well using the U2F tokens and the U2F Chrome extension.
However... and this is where my question arises:
I've also enrolled a security key for my Google account and immediately got struck by the fact that it works without using the U2F Chrome extension. As a matter of fact I've done all the Google enrollment and logins without even having the extension installed. How is this possible? I've read (some of) the FIDO specifications and saw that there may be two API levels: high - which is the u2f namespace exposed by the extension and - and low - which involves using MessagePort API. Maybe this is how Google does it? (also tried doing a chrome.runtime.connect(...) myself, but the chrome.runtime object is undefined in my web page)
Any pointer in the proper direction would be appreciated and of great value at this moment, as there aren't many resources available on this young project called U2F.
Chrome is white listing Google domains. Non-Google domains has to use the extension for now. However, this will change "very soon" according to Google -- this is documented here and mentioned by a Google developer in this webinar.
Edit: The extension is no longer required with Chrome 41. You can test it out here (Note: When accessed from and older version of Chrome, or not via HTTPS, the site will fall back to using the extension).
Is there a way through JavaScript or a web service to see if a plug-in installed in Firefox is being blocked by Mozilla? In particular, on my web site, I want to be able to tell if Mozilla is blocking an outdated version of Adobe Flash and adjust our UI accordingly.
The address that Firefox uses to download the blocklist is defined as extensions.blocklist.url preference:
https://addons.mozilla.org/blocklist/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/
Fortunately, not all of these parameters are required, this address will work to download the current blocklist:
https://addons.mozilla.org/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/21.0/
This is the ID of Firefox and the version number of the current release, so the blocklist could be different for other Mozilla applications and other Firefox versions. Looking through https://addons.mozilla.org/blocked/, there are some items listed as "for Firefox version n.n.n and higher", some are listed as "for Firefox and SeaMonkey" and others again as "for all Mozilla applications". Still, it seems that the blocklist for the current Firefox version should be the most complete one.
You can download and process this file in a web service, then adjust the behavior of your web application accordingly.
my application is setting browserhome page ,search provider ,favourites etc to all supported browsers like googlechrome,firefox,internet explorer.My purpose is to automate my application using selenium .In case of IE these informationa are stored in registry . so it is easy for me to validate the above details .But for firefox and google chrome its bit problem .So i just want know whether there is any functions available in javascript to check browser homepage ,search provider,favourites etc in firefox and google chrome ?
The simple answer is no. It would be a security and privacy issue if client side js code could access that information. Instead you would need to use a browser extension, or in your case you can just use an external program with administrative rights. I am pretty sure that selenium does not have this functionality built in, however it is all available if you know where the browser stores it. IE uses the registry, but chrome and Firefox use proprietary files in their profile directories. There may be an library that does this, otherwise it is possible