Firefox 38 released

#1

Post by AshleysBrain » Tue, May 12, 2015, 3:23 PM UTC

Re: Firefox 38 released

#2

Post by serve_yay » Tue, May 12, 2015, 2:54 PM UTC

Interesting, I had not heard of ruby before! (more info here, as linked in TFA https://hacks.mozilla.org/2015/03/ruby-support-in-firefox-de... )

Re: Firefox 38 released

#3

Post by wodenokoto » Tue, May 12, 2015, 3:15 PM UTC

serve_yay wrote: post #2

Interesting, I had not heard of ruby before! (more info here, as linked in TFA https://hacks.mozilla.org/2015/03/ruby-support-in-firefox-de... )

I was really surprised to see this wasn't implemented much earlier. Chrome apparently had support for XHTML 1.1 Ruby since 2010!

I am also surprised to see how verbose actual ruby markup is.

Better examples of mark-up on wikipedia:

https://en.wikipedia.org/wiki/Ruby_character#HTML_markup

Re: Firefox 38 released

#4

Post by malka » Tue, May 12, 2015, 3:53 PM UTC

serve_yay wrote: post #2

Interesting, I had not heard of ruby before! (more info here, as linked in TFA https://hacks.mozilla.org/2015/03/ruby-support-in-firefox-de... )

At first, I thought they added support for client side scripting in Ruby.

Re: Firefox 38 released

#5

Post by dubcanada » Tue, May 12, 2015, 3:54 PM UTC

Anyone have any insight on why they removed autocomplete from username & password fields?

Re: Firefox 38 released

#6

Post by phireal » Tue, May 12, 2015, 3:56 PM UTC

dubcanada wrote: post #5

Anyone have any insight on why they removed autocomplete from username & password fields?

Presumably this: https://bugzilla.mozilla.org/show_bug.cgi?id=956906

I think it means that sites can't overrule the browser's inclination to store passwords. The argument seems to be the browser makers will store passwords safely.

Re: Firefox 38 released

#7

Post by Touche » Tue, May 12, 2015, 3:58 PM UTC

> 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 off the list. I don't blame Mozilla as they were just following inevitability but it's a sad day for the web as there's now a lot of content that, by design of W3C, only works on certain OSes.

Of course the EME champions promised us that this wouldn't happen and they are apparently silent for the moment.

Re: Firefox 38 released

#8

Post by gear54rus » Tue, May 12, 2015, 3:59 PM UTC

dubcanada wrote: post #5

Anyone have any insight on why they removed autocomplete from username & password fields?

They removed the ability of a site maker to tell user if they should use password manager on their website. A much needed feature aka 'no, I do not care about password for your stupid site'.

Re: Firefox 38 released

#9

Post by TazeTSchnitzel » Tue, May 12, 2015, 4:01 PM UTC

> 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

Re: Firefox 38 released

#10

Post by TazeTSchnitzel » Tue, May 12, 2015, 4:02 PM UTC

Touche wrote: post #7

> 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…

> Mac OS X: Implemented a subset of the Media Source Extensions (MSE) API to allow native HTML5 playback on YouTube HTML5

Media Source Extensions, while compatible with Encrypted Media Extensions, the DRM system, are not DRM. They let JavaScript manipulate the byte streams of the video data before it goes to the video codec, so you can handle streaming and such from JS.