Page 4 of 7

Re: MX 14 Community Repository: The Firefox Thread

Posted: Wed Nov 04, 2015 9:37 pm
by mmikeinsantarosa
firefox-42.0 is now available for download from the main repo
What's new in this release:
Private Browsing with Tracking Protection blocks certain Web elements that could be used to record your behavior across sites
Control Center that contains site security and privacy controls
Indicator added to tabs that play audio with one-click muting
WebRTC improvements: IPV6 support
Preferences for controlling ICE candidate generation and IP exposure
Hooks for extensions to allow/deny createOffer/Answer
Improved ability for applications to monitor and control which devices are used in getUserMedia
Login Manager improvements:
Improved heuristics to save usernames and passwords
Edit and show all logins in line, Copy/Paste usernames/passwords from the Context menu
Migration imports your passwords to Firefox from Google Chrome for Windows and Internet Explorer; import anytime from the Login Manager
For more information check out the mozilla site.

Re: MX 14/Mepis 12 Community Repository: The Firefox Thread

Posted: Thu Dec 17, 2015 5:17 pm
by mmikeinsantarosa
firefox 43.0 is available for download from the main repo.
What's new:
Private Browsing with Tracking Protection offers choice of blocking additional trackers
Improved API support for m4v video playback
Firefox 64-bit for Windows is now available via the Firefox download page
Users can choose search suggestions from the Awesome Bar
On-screen keyboard displayed on selecting input field on devices running Windows 8 or greater
Firefox Health Report has switched to use the same data collection mechanism as telemetry

What's fixed:
Eyedropper tool does not work as expected when page is zoomed

Security fixes:
2015-149 Cross-site reading attack through data and view-source URIs
2015-148 Privilege escalation vulnerabilities in WebExtension APIs
2015-147 Integer underflow and buffer overflow processing MP4 metadata in libstagefright
2015-146 Integer overflow in MP4 playback in 64-bit versions
2015-145 Underflow through code inspection
2015-144 Buffer overflows found through code inspection
2015-143 Linux file chooser crashes on malformed images due to flaws in Jasper library
2015-142 DOS due to malformed frames in HTTP/2
2015-141 Hash in data URI is incorrectly parsed
2015-140 Cross-origin information leak through web workers error events
2015-139 Integer overflow allocating extremely large textures
2015-138 Use-after-free in WebRTC when datachannel is used after being destroyed
2015-137 Firefox allows for control characters to be set in cookies
2015-136 Same-origin policy violation using perfomance.getEntries and history navigation
2015-135 Crash with JavaScript variable assignment with unboxed objects
2015-134 Miscellaneous memory safety hazards (rv:43.0 / rv:38.5)
Check out the mozilla site for more info - mike

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 10:35 am
by dolphin_oracle
firefox 43 appears to have issues with html5 playback of youtube videos (at least).

temporary fixes:

post 1

they have been tooling around with media settings. changing this key:

media.fragmented-mp4.enabled

to

false

should let youtube work in at least html5 mode.


still exploring.... this is only a partial fix as this only gets you SD and not HD videos.

post 2
FIREFOX 43 - definitely a problem in html5 support upstream. Installing an extension that forces playback using flash brings back HD using the flashplayer.

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:05 pm
by mmikeinsantarosa
dolphin_oracle wrote:they have been tooling around with media settings. changing this key:

media.fragmented-mp4.enabled

to

false

should let youtube work in at least html5 mode.
i can fix that in the distribution.ini file and rebuild it as a +2.

If you find any more, please let me know.

I can get the +2 up to Tim later today...noonish PDT
- Mike

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:08 pm
by dolphin_oracle
mmikeinsantarosa wrote:
dolphin_oracle wrote:they have been tooling around with media settings. changing this key:

media.fragmented-mp4.enabled

to

false

should let youtube work in at least html5 mode.
i can fix that in the distribution.ini file and rebuild it as a +2.

If you find any more, please let me know.

I can get the +2 up to Tim later today...noonish PDT
- Mike
I would hold off...see bug tracker. http://www.mepiscommunity.org/firefox-and-youtube

bug logged at bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1233335

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:23 pm
by mmikeinsantarosa
I checked bugzilla and saw
Status: RESOLVED WORKSFORME
does that mean no more to be done on it?

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:29 pm
by dolphin_oracle
mmikeinsantarosa wrote:I checked bugzilla and saw
Status: RESOLVED WORKSFORME
does that mean no more to be done on it?
good questions. I just added our experiences in an effort to wake someone up. Doing some quick googling, there are various fixes, most involve forcing usage of adobe flash rather than html5. most are posting these without actually realizing that's what they are doing.

the media.fragmented fix above will work, but it disables HD playback. and I think it will only work for new installs, since those settings go into the user profile. might be wrong on that one though.

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:32 pm
by mmikeinsantarosa
Maybe firefox should start going back into test first :confused:

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:39 pm
by Jerry3904
Until we get this resolved one way or the other, shouldn't we pull the package?

Re: MX 14 Community Repository: The Firefox Thread

Posted: Fri Dec 18, 2015 12:42 pm
by richb
Jerry3904 wrote:Until we get this resolved one way or the other, shouldn't we pull the package?
I agree with that. It is a major problem and no need to put it into test since we already know it fails.