Google reCAPTCHA is not working on IE9 (compatibility view is disabled). It loads correctly but the checkmark is not clickable. After some seconds, the checkmark disappears and it shows:
Please upgrade to a supported browser to get a reCAPTCHA challenge.
Alternatively if you think you are getting this page in error, please
check your internet connection and reload.
It also throws the following error:
'MessageChannel' is undefined
It looks like Google reCAPTCHA is no longer supported on IE<10 since the Channel Messaging API is not supported.
Is there any way to make it work on IE9? Has anyone been able or at least tried to port the Channel Messaging API?
Thanks!
Did you installed any windows security updates?
Did you change any group policy like 'Turn off Data URI support'?
If yes, then try to enable this policy or for a testing purpose try to remove that security update may solve the issue.
Also try to make a test with other browsers and check whether you have same issue with those browsers or it works correctly.
It can help us to narrow down the issue.
You can let us know about your testing results. We will try to provide you further suggestions.
Regards
Deepak
Related
I have this web application login page that calls FB.GetLoginStatus() from the Facebook JavaScript SDK after the document is done loading. This worked perfectly fine on all browsers (mobile included) and that was the happily ever after.
BUT, one day, out of plain nowhere, I notice that the SDK is failing to get the login status data of the Facebook user when the page is done loading. I take a look in the console and I see something around the lines of
Load denied by X-Frame-Options [massive link generated by the SDK]
does not permit framing.
Here's what bugs me: this works perfectly fine in Safari. I was introduced to the error when I opened the web app on Chrome (same error as quoted above, slightly different wording). I tried on Firefox and got the same thing. I spent a few hours trying to find a cause but failed and went to sleep.
I wake up the next day and miraculously it's now working on Chrome (?) without me having done any changes (?!). But, for some reason, the error persists only in Firefox now.
Does anyone have a clue what this might be? Something that Firefox does differently that Safari and Chrome don't?
A clue here is that I'm using a tunneling service (ngrok) and I don't have a signed certificate for it, thus I get the casual (you're entering an 'unsafe' website, blah blah blah). Perhaps Firefox is blocking the SDK because the connection is not secure?
Any insight on this would be marvelous. Thanks 🙂
OK, after fighting this for a few hours I finally found out what was bothering Firefox: the website site URL field in the app's Facebook Dashboard settings.
The issue wasn't even with ngrok or a missing signed certificate, it was the fact that the website in the settings had the production domain (.app) instead of the ngrok one I'm currently using for development (eu.ngrok.io).
The only reason I managed to pinpoint this back to the dashboard settings is because I have 2 Facebook apps, and the other one was working fine, so I imagined it might be a misconfiguration in the settings that was causing the issue (Facebook has a shitty standard in place for explaining/handling errors — it's like shooting in the dark until you hit something when using their SDK's).
What I don't understand here is why the heck only Firefox seems to have a problem with this setting being misconfigured or why the issue disappeared out of nowhere from one day to the next for Chrome. Anyways, if I managed to help anyone else fix anything similar with this thread than this headache has been worthwhile.
Peace out ✌🏽
My web app is failing when I test it in BrowserStack, it breaks in the detectizr.js file, where navigator.plugins is being accessed. When I look at the navigator object via dev tools, I can see that for plugins there is a message saying permission denied and want to confirm if this is why my web app breaks in IE Edge and no other web browser. Has anyone encountered this issue? I am wondering if perhaps it's only an IE14 Edge setting that needs to be changed.
I've seen this same issue in IE Edge on BrowserStack when accessing navigator.plugins. I am using socket.io-client.js which uses this check to see if Flash is enabled. I don't see this issue on my actual Windows computers, so I believe you are on the right track that it is something specific to BrowserStack.
sorry - i wanted to comment not answer, but i don't have a good enough reputation to comment yet. guess i'm not allowed to be helpful yet :(
I used to test whether a logged-in user could hit the Skype CDN to determine whether or not to show them UI elements:
https://cdn.dev.skype.com/uri/skype-uri.js
But it seems like, out of nowhere, their CDN just moved (breaking my code) to here:
http://www.skypeassets.com/i/scom/js/skype-uri.js
My page is https and I can change the url above to https a la:
https://www.skypeassets.com/i/scom/js/skype-uri.js
But because there is no valid certificate there I can't connect and the browser doesn't throw the "confirm security exception" message.
What are my options to determine if I can connect to Skype CDN from SSL?
They were made aware of it by a developer here over a month ago.
To sum it up:
They are now aware of the problem.
They're deploying a fix shortly.
It might still cause issues with Chrome.
Seems like you'll just have to hang tight, sorry.
Here is their full official response:
Hi,
Thanks for posting, URIs are supported by the Skype Developer team and you can find out how to contact us by visiting the contact us page on http://developer.skype.com.
I can confirm that using Skype URIs on secure connections is presently broken. We have identified a fix and hope to deploy it shortly. Its likely, however, that the fix will still not work on newer versions of the chrome browser due to a change in the way it handles iframes launched over secure connections.
Allen Smith
Skype Developer Support
Update
7 months later and they still haven't properly fixed it.
However, that same thread now has a solution (of sorts) in its last comment:
Copy skype-ui.js to your project and replace below code to:
this.SkypeClientDownloadUrl = this.httpProtocol +
"//secure.skype.com/download"; this.assetPrefix = this.httpProtocol +
"//secure.skypeassets.com/i/scom/images/skype-buttons/";
this.analyzeScript = this.httpProtocol +
"//secure.skypeassets.com/i/scom/js/" + "skype-analytics.js";
Not pretty by any means, but at least it seems to work.
In a Chrome Extension, I'm trying to get gmail compose body content.
An error jumps out sporadically, and does not prevents it from working.
This is being run as a content script. I believe permissions are not the issue here, because when there is a permission missing, the error is different and the operation is blocked by Chrome, definitely not the case.
Error comes out in this line:
encodeURIComponent($canvas.find('iframe').contents().find('body').text());
where
var $canvas = $('#canvas_frame').contents();
Any information on this error and a possible turnaround?
You can not read cross site content using javascript. XSS Auditor of Google Chorme will never allow this.
Please have a look at http://en.wikipedia.org/wiki/Same_origin_policy
UPDATE 1 -
There is support for cross site communication using window.postMessage() in Chrome 2+. Please have a look at this documentation https://developer.mozilla.org/en-US/docs/DOM/window.postMessage
To give a good answer, we need more information:
where exactly you are running this code, is it in the web page, the extension's content script or the etension's background script?
Also, what does your manifest.json file look like? Which sites have you asked for permission to run on.
I suspect this is a case of a badly-written error message and really it is saying: your extension does not have permission to run on apis.google.com. In that case, simply add permissions for apis.google.com. More details are in the Chrome extensions docs: http://developer.chrome.com/extensions/manifest.html#permissions
I have an HTML5 page loaded on server along with a geolocation script. The code is working and has no errors. It shows the position and map the user. Right now, it's working well for everyone else and i also tried the same on other PC and it works. But, when i visit the page on my Chrome browser, nothing shows up. Why is that happening? Why can't it locate me and map me? I have Windows 7 OS running the latest Chrome and using data-card for internet.
This is the LINK
On the other hand, the Google page accurately shows my location on the left bar side
That page detects my location correctly in Chrome 17 (dev channel). I do see a JavaScript error, however: "Uncaught ReferenceError: geocoder is not defined" on line 81 of myLoc.js. Taking a quick look at the code, it doesn't appear to be defined anywhere. Have you perhaps forgotten to include a file?
I experienced the same issue with geolocation script. It seems to be an issue with Chrome specifically blocking the uri starting with "file:///" for security reasons.
See related articles:
http://groups.google.com/a/googleproductforums.com/forum/#!category-topic/chrome/give-feature-feedback-and-suggestions/E0yx7wne-RI
http://groups.google.com/a/googleproductforums.com/forum/#!category-topic/chrome/report-a-problem-and-get-troubleshooting-help/pNcftbZTN1E
HTML 5 Geo Location Prompt in Chrome
Check in your chrome, in settings -> advanced -> privacy (content) -> localization if you allow web pages to check your location (this menus can be named a bit different, I'm checking on Polish Chrome).
You say nothing shows up and the question to allow web page to check location should show up (this happens by me).
Another thing, geolocation is checked by Wi-Fi if available, determine it by your IP may be quite inaccurate.