i am working a social network platform and wanted to integrate the live streaming services and also the chat voice and audio calling services. they are all active, except that I keep getting "Sorry your browser does not have webrtc" even after installing this extension on all my browsers, it still says the same for Chrome, Firefox, and Microsoft Edge. The only browser working perfectly well is the apple safari browser. Now I don't know how to fix this.
WebRTC has to work under https environment. That's why your website isn't working. Deploy the application with SSL security.
Related
I am looking for a handwriting recognition API that I can embed in my web application.
I found this: Handwriting Recognition API from Google.
The post also refers to a Demo.
It is my understanding that this API works in all (newer) Chromium based web browsers, i. e. Google Chrome or MS Edge.
I opened the demo in both browsers (Google Chrome 106.0.5249.119 and MS Edge 106.0.1370.42) on my Win-11-64-bit machine. Same error message in both browsers:
Handwriting recognition API is not supported on this platform.
Any idea why I get this error message? Is there anything I can do to fix this?
I have made this application using Leaflet.js with these plugins: MarkerCluster, Leaflet Map Fullscreen, it's hosted in a Linux server, HTTP apache2.
For some reason, I can't get my current location on the following browsers:
Mozilla Firefox (latest version)
Google Chrome (latest version)
Microsoft Edge
In IE, it gives me the popup to give permission to locate myself, and it works... only once. If I try to locate myself again it behaves like the other browsers above.
And, if I open the link in Instagram dm's it works just fine...
It works also in localhost or if I use location guard browser extension to make my location a fixed point.
What's causing this issue? Is it because it isn't https?
You will have to switch to https if you want to support geolocation on most if not all modern browsers.
For Chrome
Starting with Chrome 50, Chrome no longer supports obtaining the
user's location using the HTML5 Geolocation API from pages delivered
by non-secure connections. This means that the page that's making the
Geolocation API call must be served from a secure context such as
HTTPS.
For Firefox
This feature is available only in secure contexts (HTTPS) [...]
And according to the nice support grid on MDN, Opera and Safari should also require https to enable geolocation.
I'm using W3C Browser Web Speech Api. I search everywhere but i cant find it answer. Is there any limitation for usage ?
Demostration: https://www.google.com/intl/en/chrome/demos/speech.html
Yes, with a bit of a catch. I finally hit a limit recently after a lot of experimentation; as soon as a request starts, it's cut short.
On a desktop web browser (Chrome), there's a limit for each user (Primiano Tucci works at Google, so I'd trust him!), and you can't buy more time with the API.
However, as you could see from the first link, the exception appears to be Chrome on Android, which apparently has no limitations because it accesses an internal API for speech recognition when visiting web pages that use the Web Speech API.
For desktop browsers, you're out of luck unless you can assume users don't mind a limit. Even Annyang and voice dictation in Google Docs aren't working for me at the moment, while online voice recognition services that don't go through Google are working.
From my testing with Chrome Version 87.0.4280.141 (Official Build) (64-bit), it appears to stop after 5 minutes on Windows 10 Pro.
I am using an iframe to embed video from Vimeo in our Moodle LMS. My code works perfectly in Chrome, IE and Firefox, but not Safari. I am using the standard Vimeo API to embed the video. I know the issue is SSL related because I can remove the S from HTTP in the url and the embedded video works perfectly. I can't run our LMS in an unsecured environment, and the videos are no threat, but vimeo will not stream their video using ssl because of the overhead. Anyone have a solution that works across all browsers?
Vimeo's Embedding Videos FAQ page indicates that it does support HTTPS. Are you following these instructions?
Can I embed my video on an HTTPS domain?
You sure can!
Our embed code is now “protocol relative,” which means that we adhere to the protocol of your website, whether it’s HTTP or HTTPS.
If you’re using an older version of the Vimeo embed code (with a http://player.vimeo.com URL within it), you’ll simply need to change “http” to “https” and it should start working!
and
Why doesn't my video load when I preview it in my website editor?
Vimeo's embed code uses protocol-relative URLs, meaning that we automatically match the embedded video's protocol to your website's — either HTTP or HTTPS.
If you are previewing your website with a program like Dreamweaver, the video will not load because the program cannot determine the correct protocol to use. That said, the video should work flawlessly once you publish it.
There are two ways you can test your embed:
Add http:// to the player.vimeo.com URL in your website's source code. This should allow you to see the embed in preview mode.
Publish a live test page where you can see the embedded video in action.
Is there any options to test websites in device browsers by using Testcomplete? Testcomplete has opetions like virtual browser in desktop but i need to automate my websites in default browsers in real device.
Web testing on real mobile devices isn't supported as of now, but you can submit a feature request.