Announcement

Collapse
No announcement yet.

Firefox 36 Brings Full HTTP/2 Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GreatEmerald
    replied
    No group chat in Firefox Hello yet? Sigh. Will continue to use appear.in, then.
    MSE is welcome, though.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by ssokolow View Post
    I vaguely remember "partial" just meaning that they only implemented the parts YouTube actually used, rather than features that would be used for... say... some kind of in-browser non-linear video editor.
    I wish it's enough also for Netflix

    Leave a comment:


  • Luke
    replied
    Concern with the way Firefox is going

    As I see all this discussion about "media source extensions" for Youtube, I have a concern: is Firefox going to make changes down the line that break compatability with using the gstreamer H264 codec instead of the Cisco one? I only connect to Youtube/Google through Torbrowser but use Firefox for non-ad supported video a lot, using the gstreamer codecs in HTML5.

    I have had to make a lot of configuration changes in recent versions of Firefox to prevent it from phoning home. In particular, I cannot use the Cisco codec or it's auto-updater (GMPInstallManager) and have to replace URL's with empty strings in about:config in order to disable the checks. This is to ensure that neither Mozilla nor anyone else gets a list of all IP addresses I use. If the ability to change/erase these URL's gets removed as a feature the developers/target users don't use, I could block the phone-home URL's in /etc/hosts but first would have to know them.

    As some point I suppose I will have to permanently pin Firefox to a last good version (perhaps an ESR version?), switch browsers, or locally compile Firefox as a non-tor browser with all the rest of the Torbrowser privacy changes included. The worry is that some "feature" that puts privacy at risk will come along without a switch in about:config to disable it, or without which current non-Youtube, DRM-free video will break. BTW, I can play 1080p Archive.org video right now in Firefox if I am somewhere with enough bandwidth available, using the gstreamer codec. I don't mind having to disable stuff locally as long as I know what it is. The only reason I am aware of the GMPINstallManager issue is it shows up in terminal, I run Firefox from a script that runs it with the .mozilla directory copied into a tmpfs to defeat both persistant supercookies(tested-it works) and hostile data recovery in the event an attacker (after a raid or "burglary")manages to defeat my disk encryption.

    Essentially my needs in the browser itself are the same as those of the Tor project in setting up Torbrowser, except for using a direct connection to the Internet where Tor use is not necessary and would waste Tor bandwidth.

    Leave a comment:


  • schmidtbag
    replied
    Originally posted by 89c51 View Post
    Even accelerated FF still has high CPU. Someone explained it here in the forums and had to do with the way it renders on the screen if i remember correctly.

    And yes MES is needed, GTK3 also wayland also etc etc.
    With MSE right around the corner, that's one thing off the todo list. If GTK3 is done properly, wayland should work too. If the way they use GTK3 affects the rendering, CPU usage should drop. GTK3 could seriously benefit firefox.

    Leave a comment:


  • 89c51
    replied
    Originally posted by schmidtbag View Post
    I know right? About time. Though I'm not really keen on the word "partial" being used. I just hope I can get decent 1080p video playback, and preferably lower CPU usage. I'm not entirely sure but I think FF is now the most CPU-heavy browser, while Chrome is the most RAM heavy.
    Even accelerated FF still has high CPU. Someone explained it here in the forums and had to do with the way it renders on the screen if i remember correctly.

    And yes MES is needed, GTK3 also wayland also etc etc.

    Leave a comment:


  • eydee
    replied
    Originally posted by AnAkIn View Post
    If you use Firefox Developer Edition everything except MSE & H.264 will be green, and even that can be enabled with a pref.
    Sure, just pointing out that the current state is not worth being news yet.

    Leave a comment:


  • AnAkIn
    replied
    Originally posted by samdraz View Post
    strange, they just removed the line metioning 'media source extensions'.

    so i download firefox for x86_64, they do have two option for mediasource on mp4 and youtube and webm separately along with 'mediasource.enabled' toggle
    They didn't remove the line. One was the changelog for the beta channel (from January) and the other for the release channel (from today). It's almost always different.

    Originally posted by eydee View Post
    On the youtube.com/html5 page MSE is still all red. That partial implementation must be very partial at the moment.
    If you use Firefox Developer Edition everything except MSE & H.264 will be green, and even that can be enabled with a pref.

    Leave a comment:


  • eydee
    replied
    On the youtube.com/html5 page MSE is still all red. That partial implementation must be very partial at the moment.

    Leave a comment:


  • samdraz
    replied
    strange, they just removed the line metioning 'media source extensions'.

    so i download firefox for x86_64, they do have two option for mediasource on mp4 and youtube and webm separately along with 'mediasource.enabled' toggle

    Leave a comment:


  • AnAkIn
    replied
    Release notes from today:

    https://www.mozilla.org/en-US/firefo.../releasenotes/

    There's no MSE yet, it's still only on beta.

    Leave a comment:

Working...
X