Does WebRTC fit in this library?
mseddon opened this issue · 3 comments
It is currently supported in Firefox, Opera and Chrome. Microsoft have no plans to support it in Trident at this time in favor of adopting their own, competing standard... (Oh, horay, that again). That said, they u-turned on WebGL. The api is technically not browser specific, although I'm not sure what the policy is in this situation.
This actually leads on to a wider question- if a particular browser does not implement a feature, say, WebGL, do we provide a simple method to detect this fact, or is the user of the library forced to drop down to Dynamic hackery to probe the existence themselves? Perhaps this (and general browser version detection) would be a useful addition to org.scalajs.dom.extensions, or would it be better suited as a complementary project that one can optionally link in?
Tough call =/ I'd say for now "keep it out"? I can imagine that most people who need to write websites won't be willing to turn away 1/3 of the people on the internet. Perhaps you can publish it as a standalone library, and maybe we can take another look in a few months/a year if IE dwindles in market share or Microsoft decides to join in on WebRTC.
Ok, sure, that seems reasonable. Thanks!
Closing this for now, feel free to reopen if/when you want to continue discussion =)