Safari vs Browser Widget

[hh via use-livecode]

I am working on a HTML5 web page that accesses the device's camera.
When I open the url in Safari (on my Mac or iOS device), I am asked
if it's ok to use the camera and everything works perfectly!
However, if I load this same url in the Browser Widget (or a plain
native browser), it doesn’t ask to use the camera and it all fails.
Is this a limitation of the implementation of the browser in LiveCode,
or is there a setting I have to set?

The getUserMedia() dialog doesn't work in the browser widget.
You could try to do that "as javascript" in your HTML5 app.

We meanwhile know that Dan needs it for mobile onl, so a HTML5
standalone will not work for that.

To demonstrate this works on desktop with a HTML5 standalone try this
with Chrome, Firefox or Safari (use newest):

http://hyperhh.de/TEST/GUM/GUMX.html

This is *very* basic, a first step into WebRTC.

Your webcam is started from the standalone, the mediaDevice dialog
and the video display is in the webpage. The display could be 'moved',
with loosing some frames/second, to the standalone.

[hh via use-livecode]

Some of the newer browser versions need a https connection. So if
http://hyperhh.de/TEST/GUM/GUMX.html doesn't work, then please try

https://hyperhh.de/TEST/GUM/GUMX.html

Post by hh via use-livecode

I am working on a HTML5 web page that accesses the device's camera.
When I open the url in Safari (on my Mac or iOS device), I am asked
if it's ok to use the camera and everything works perfectly!
However, if I load this same url in the Browser Widget (or a plain
native browser), it doesn’t ask to use the camera and it all fails.
Is this a limitation of the implementation of the browser in LiveCode,
or is there a setting I have to set?

The getUserMedia() dialog doesn't work in the browser widget.
You could try to do that "as javascript" in your HTML5 app.

We meanwhile know that Dan needs it for mobile onl, so a HTML5
standalone will not work for that.
To demonstrate this works on desktop with a HTML5 standalone try this
http://hyperhh.de/TEST/GUM/GUMX.html
This is *very* basic, a first step into WebRTC.
Your webcam is started from the standalone, the mediaDevice dialog
and the video display is in the webpage. The display could be 'moved',
with loosing some frames/second, to the standalone.

[Brian Milby via use-livecode]

This is pretty cool.  It does work on my iPhone (https).

Thanks,
Brian

Post by hh via use-livecode
Some of the newer browser versions need a https connection. So if
http://hyperhh.de/TEST/GUM/GUMX.html doesn't work, then please try
https://hyperhh.de/TEST/GUM/GUMX.html

Post by hh via use-livecode

I am working on a HTML5 web page that accesses the device's camera.
When I open the url in Safari (on my Mac or iOS device), I am asked
if it's ok to use the camera and everything works perfectly!
However, if I load this same url in the Browser Widget (or a plain
native browser), it doesn’t ask to use the camera and it all fails.
Is this a limitation of the implementation of the browser in LiveCode,
or is there a setting I have to set?

The getUserMedia() dialog doesn't work in the browser widget.
You could try to do that "as javascript" in your HTML5 app.

We meanwhile know that Dan needs it for mobile onl, so a HTML5
standalone will not work for that.
To demonstrate this works on desktop with a HTML5 standalone try this
http://hyperhh.de/TEST/GUM/GUMX.html
This is *very* basic, a first step into WebRTC.
Your webcam is started from the standalone, the mediaDevice dialog
and the video display is in the webpage. The display could be 'moved',
with loosing some frames/second, to the standalone.

_______________________________________________
use-livecode mailing list
http://lists.runrev.com/mailman/listinfo/use-livecode

[Mark Wieder via use-livecode]

Post by Brian Milby via use-livecode
This is pretty cool.  It does work on my iPhone (https).

It's *very* cool, especially since it works in Chrome on linux, where
the browser widget doesn't work.

[Bob Sneidar via use-livecode]

Ditto.

Bob S

This is pretty cool. It does work on my iPhone (https).
Thanks,
Brian