> Ruby annotation support Finally! After only 24 years, East Asian languages get some attention. Perhaps next Western browser makers might consider vertical text support. sigh
Firefox 38 released
21–30 of 133 posts
Re: Firefox 38 released
#22> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…
Does EME being implemented finally mean that I can uninstall Silverlight for watching Netflix in Firefox in the near future?
Re: Firefox 38 released
#23> Ruby annotation support Finally! After only 24 years, East Asian languages get some attention. Perhaps next Western browser makers might consider vertical text support. sigh
Vertical text support is coming on quickly in Firefox. There’s still a bunch of blockers, but they’re being knocked off fast: https://bugzilla.mozilla.org/show_bug.cgi?id=145503
Re: Firefox 38 released
#24> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…
What video could you watch before that you cannot watch now? I also wish we lived in a world which didn't need EME but it's not like the status quo was video which played for everyone. It just meant that everyone had to download monthly updates to avoid security problems with the massive plugin they used to play video and Linux, etc. users were largely still screwed.
Whenever this happens, usability suffers as well. And we had a real opportunity here to give users an open and non-broken standard as an alternative, on top of which alternative platforms for content delivery could be built, alternatives that could have won simply because of the ubiquitousness of the standard browser.
Besides, DRM is technically and fundamentally broken. All my respect for W3C has gone down the window.
Re: Firefox 38 released
#25> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…
I'm not sure how this is any different from following the ongoing development of any other feature that requires platform-specific code to be written (WebGL, etc.). You will periodically see updates that only pertain to one platform or another, especially during bringup. No conspiracy there.
Re: Firefox 38 released
#26> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5 > Implemented Encrypted Media Extensions (EME) API to support encrypted HTML5 video/audio playback (Windows Vista or later only) HTML5 > Automatically download Adobe Primetime Content Decryption Module (CDM) for DRM playback through EME (Windows Vista or later only) :( Notice which OSes are left o…
Re: Firefox 38 released
#27> CRITICAL Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. Uh, glad they fixed this one, but it sounds pretty bad. I'd kinda like to see the actual CVE/bug report.
Re: Firefox 38 released
#28> CRITICAL Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. Uh, glad they fixed this one, but it sounds pretty bad. I'd kinda like to see the actual CVE/bug report.
Re: Firefox 38 released
#29Earlier quoted context omitted.
Does EME being implemented finally mean that I can uninstall Silverlight for watching Netflix in Firefox in the near future?
Don't do it. I've been using the non-silverlight Netflix in Safari and it's such a nightmare I switched back. Constantly fails to load content.
Re: Firefox 38 released
#30Earlier quoted context omitted.
Does EME being implemented finally mean that I can uninstall Silverlight for watching Netflix in Firefox in the near future?
Don't do it. I've been using the non-silverlight Netflix in Safari and it's such a nightmare I switched back. Constantly fails to load content.