4 ms·
> chrome is currently the only browser that fully supports all html5 features. Well, no. No browser fully supports all HTML5 features. It's all a work in progr
by azakai 13y ago
> chrome is currently the only browser that fully supports all html5 features.
Well, no. No browser fully supports all HTML5 features. It's all a work in progress.
I guess your app happens to use features present in chrome, but other browsers lead in other areas. Off the top of my head, firefox had webrtc binary datachannels (important for multiplayer games) earlier. And a comment above mentions ES6 generators as well.
- cpncrunch 13y agoBasically Chrome supports all of the HTML5 features that we use (audio/video, drag+drop, screen sharing), whereas firefox doesn't. Perhaps there are features that firefox supports that chrome doesn't, but I haven't come across any.
- kbrosnan 13y agoDrag and drop has been supported since Firefox 3.5. https://developer.mozilla.org/en-US/docs/DragDrop/Drag_and_Drop https://developer.mozilla.org/en-US/docs/DragDrop/Drag_and_D... Screen sharing via get user media was added in this release Fx27, https://bugzilla.mozilla.org/show_bug.cgi?id=742832 https://bugzilla.mozilla.org/show_bug.cgi?id=742832 Audio/Video support has been in Firefox since Firefox 3.5 https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_HTML5_audio_and_video https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Usin...
- cpncrunch 13y agoAs I said in my original comment, firefox supports drag+drop uploads, but not images from websites. You can drop an image from your hard drive, but you can't drag an image from another website. Chrome lets you do this. Tab sharing isn't screen sharing. Chrome lets you share your entire screen, not just a tab. As I said in my original comment it is getUserMedia audio that is buggy on firefox (it cuts out after 5 seconds), not audio in general. Luckily there is a hack to get it working: https://support.mozilla.org/en-US/questions/984179 https://support.mozilla.org/en-US/questions/984179. Looks like it might be a garbage collection bug - it's not seeing the reference to the input device from the script processor node.