Is there a way to launch either Google Chrome or Mozilla Firefox from the commandline so that it automatically plays the video on the specified URL (motogp.com in this case) in fullscreen mode?
Installing additional extensions would not be a problem.
Related
We are developing web for kiosk based on Android OS. I am trying to use the webcam for qrcode recognition, it works fine in Firefox but the camera is not recognized in Chrome. Even if you call MediaDevices with js code, video input does not come out only in Chrome. Can anyone guess the cause?
I created a simple HTML page with a link to an RTSP stream. However, when I open the page in Google Chrome, and click the RTSP link, nothing happens. No errors are emitted in the F12 Chrome Dev Tools either.
I would expect that clicking the link would invoke an external program to open the link. I have VLC on Windows 10 selected as the "default app" for video playback.
Video Feed
When I open the same link in Firefox, I receive the following error:
The address wasn’t understood
Firefox doesn’t know how to open this address, because one of the following protocols (rtsp) isn’t associated with any program or is not allowed in this context.
You might need to install other software to open this address.
Question: How can I get an RTSP link to prompt me to open an RTSP stream with a video player installed locally, in Google Chrome on Windows 10?
I am using videojs to use HLS in Chrome but for a particular URL this fails (CORS issue) but in Safari it plays without problems.
I have a code in videojs but for figure out the problem faster, I used you this online player:
https://videojs.github.io/videojs-contrib-hls/
For this file, problem is present in Chrome (but not in Safari):
https://s3-us-west-2.amazonaws.com/andy-mediaconvert-tests/Haystack.tv/2019-05-10_Output/02_qvbr_ch1/ch1_hd720.m3u8
Other link like this works in both:
https://d2ufudlfb4rsg4.cloudfront.net/bloomberg/IIrcyflxg/IIrcyflxg_medium.m3u8
Then, my question is, why Safari can play a video with CORS issue but Chrome not?. Or how Safari avoid the CORS issue? to try to reproduce it in Chrome.
CORS is enforced by the browser, not the server. So it’s up to the browser whether the resource is blocked or accessed. In the case is chrome, the video segments are downloaded via XHR, and therefore are handled by the browser HTTP stack. In the case of safari, which natively supports HLS, the segments are downloaded by the media player directly, bypassing the browser, and thus CORS.
This behavior can not be reproduced in chrome.
I've already disabled all plugins in Chrome.
In firefox we can go to about:config and set media.play-stand-alone;false andplugin.disable_full_page_plugin_for_types;application/pdf,audio/mpeg
How can we do this for Google Chrome?
I have a chrome extentions to record and upload sound. I embedding some flash content in an iframe to that extention. The flash part is requesting access to the allow the michrophone first. If I open in browser firefox and chrome, it's work proferly. But if open in chrome extentions, allow button is disabled or can't be clicked.
are there any way to fix this?
Thanks......
There are security restrictions embedding flash inside a chrome-extension:// URL, which behaves much like a sandboxed file:// environment. Perhaps you're running into one.
Here are some bug links for you:
http://code.google.com/p/chromium/issues/detail?id=42796
http://code.google.com/p/chromium/issues/detail?id=58909
A potential workaround is to have an iframe point to an HTTP url with the flash content. You can also make an exception in the flash control panel, but that's per machine and probably not what you want.