W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Re: What is missing for building "real" services?

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 16 Jan 2014 09:59:50 +1100
Message-ID: <CAHp8n2mgCppc-QCoMVwnUMzPmCMuh-p8Lq-J51P_VWsBoXBppw@mail.gmail.com>
To: Tsahi Levent-Levi <tsahi.leventlevi@gmail.com>
Cc: public-webrtc <public-webrtc@w3.org>
On Thu, Jan 16, 2014 at 6:01 AM, Tsahi Levent-Levi
<tsahi.leventlevi@gmail.com> wrote:
> Hi guys,
> One of the things that I am seeing is the lack of support in websites.
> WebRTC works great on a webpage, but not in websites. This means that it
> makes perfect sense to use it in SPAs (single page application), but if I
> want to embed it into a website (an ecommerce one for example) - it is far
> from easy - the moment the user leaves the page in favor of another one -
> the call drops.
> This causes a lot of vendors offering click-to-call services that get
> embedded into websites to open up the video/audio session in a separate
> browser window, which then doesn't float around. The experience you get is
> broken due to that.
> Fixing this by having a way for the service to express the fact that it
> wishes to maintain WebRTC sessions across web pages within the same domain -
> or in any other way - will imrpove usability.

Hmm, interesting challenge. I don't think there is a way to retain
objects between navigations, not even same-domain.
You can create a separate browser window with window.open() [1] and it
remains open while navigating. But it doesn't stay on top FAICT.

[1] http://www.quirksmode.org/js/popup.html


> On a similar note, it would be nice to be able to float the video on top of
> the screen - not the browser window, but the whole desktop (and mobile).
> This enables looking at things in parallel to the conference and still
> having context or the ability to see the people you are talking to.
> Call it my two cents...
> Regards,
> Tsahi Levent-Levi
> http://bloggeek.me
Received on Wednesday, 15 January 2014 23:00:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:54 UTC