search

Cloudkibo / CloudKibo

CloudKibo
0 stars 0 forks source link

CloudKibo completely broken on MS Edge browser #150

Closed sojharo closed 8 years ago

sojharo commented 9 years ago

My computer got upgraded to windows 10 yesterday. I had heard that MS Edge (new browser) is supporting webrtc now. I came to know that cloudkibo was completely broken on the MS Edge and also its developer tools and consoles showed me nothing. This never happened on chrome and firefox. This is a new browser and people would like to try this new browser. If webrtc is still not supported in Edge then it should at least work with non-webrtc parts like angularjs application with chat in socket.io. Application loads the webrtc modules when it is launched maybe it is broken because of webrtc modules.

kiboedge

kiboedge2

jekram commented 9 years ago

Yes they are supporting WebRTC but the next updated version webrtc 1.1 or some thing like that.

This is Good that IE will be supporting it.

Let's get our Chrome and FireFox working then we would tackle IE.

sojharo commented 9 years ago

During meeting today, we were able to see the home page of cloudkibo correctly. It means the issue is not of angular js.

Also the issue only appeared on page which open after we sign in. In this page, we have webrtc code. It is breaking because of webrtc code like window.getUserMedia we use.

Saba was doing comparison of plugins. I think including any one of them in our website might fix this issue.

Same is the case for #210 and #211

sojharo commented 9 years ago

IMPORTANT:

Microsoft Edge is going to support ORTC instead of WebRTC. Also, the MS Edge doesn't support plugins, we can't hope that plugin like TemaSys would work with it.

https://bloggeek.me/ortc-edge/

In the above article, also see my comment and answer from Tsahi.

jekram commented 9 years ago

@sojharo

Thanks for sending the article I also saw it last night.

  1. So it doses not make sense to pursue TemaSys. We would stop all effort on following the plugin work.
  2. For IE we should ignore all browsers except for Edge. We should put a message in CloudKibo that this browser is not supported. Please try Chrome or Firefox.
  3. When Edge is working for us. We would change the above message to: Please try Chrome or FireFox or Edge.
  4. We would ignore Safari until they come up with a WebRTC solution.
  5. In KiboSupport if a user is coming from IE or Safari we should not give them the option to connect to CloudKibo. Because it would not, work. In that case, we should limit it to chat and ask the user to install Chrome or Fire Fox.
  6. We need to understand when and how to implement Edge.

@sojharo Do you agree we should abandon plug-in?

Regards

Jawaid

sojharo commented 9 years ago

In Windows 10, both MS edge and Internet Explorer are available. With advent of Edge, IE have not been replaced. I am not sure how long it will take to completely take IE out of future releases.

I am sure that for Safari, we would need plugin as long as Safari doesn't support WebRTC. Plugin will only not work in MS Edge nor will WebRTC be supported in this browser.

Only reason for plugin is Safari now. As I think, it won't take longer for IE to disappear from future Operating Systems. Maybe, there is a less number of users using IE after release of Edge. Not sure about how the users are divided in these browser.

I have included a discussion slide on above points in deck.

jekram commented 9 years ago

@sojharo Please let me me what will be the effort to do plugins and would it work?

sojharo commented 9 years ago

Yes, let me include this task in the deck. I would need to look into these plugins myself.

sojharo commented 9 years ago

Temasys:

WebRTC Everywhere

The third one easyRTC is an SDK / library and can not be used with our application.

jekram commented 9 years ago

Thanks. Is your recommendation Temasys? If we need screen sharing how much we have to pay?

jekram commented 8 years ago

We will reopen this when IE is ready.