Meet the browser: Firefox Next

By bogas04
in Web Browser Discussion & Support

 Share

Recommended Posts

Grand Master

+Red King Subscriber²

Posted
  • Subscriber²
Posted

Mozilla adds -webkit prefix emulation to select sites in Firefox

 

 

The emulation is hardcoded into Firefox 39 which means that it will only work on a list of sites that Mozilla added to it specifically.

?

?

Thanks Webkit. /s
Veteran

BooBerry

Posted
Posted
1158289 - Optimize Reader View's line length to have between 45 and 75 characters
    fixed in 40, uplift requested
1158281 - Match Pocket's Reader View Sepia Theme
    fixed in 40, uplifted to 39 and 38.
1158294 - Increase Reader Views Default Type Size
    fixed in 40, uplifted to 39 and 38.
1158302 - Increase the Font Size of Reader's H1 and H2 Headers
    fixed in 40, uplifted to 39 and 38.
1149068 - Reading List Toolbar Sans Serif font button always displays Helvetica
    fixed in 40, uplifted to 39 and 38.
1149136 - Incorrect hover styling for remove button in Reading List sidebar.
    FIXED in 40, uplifted to 39 and 38.
1149520 - Reader mode toolbar repaints during font size change
    FIXED in 40, uplifted to 39 and 38
1149649 - Design Polish Updates for the Reader View Footer
    FIXED in 40, uplifted to 39 and 38
1148762 - Reading List causes scroll bar to flash when opening sidebar
    FIXED in 40, uplifted to 39 and 38
1149261 - Improve the Reader View Close Button
    FIXED in 40, uplifted to 39 and 38
1147444 - Improve the transition when deleting an item from the Reading List
    FIXED in 40, uplifted to 39 and 38
1147440 - Improve the transition of the Add to Reading List URL Button
    FIXED in 40, uplifted to 39 and 38
1147479 - Improve the transition when adding an item from the Reading List
    FIXED in 40, uplifted to 39 and 38
1137211 - Font panel should disappear when clicking margins
    FIXED in 40, uplifted to 39 and 38
1145809 - reader view footer area
    FIXED in 40, uplifted to 39 and 38
1148050 - Type Control Visual Improvements
    FIXED in 40, uplifted to 39 and 38
1132656 - Toolbar overlaps content in narrow windows
    FIXED in 40, uplifted to 39 and 38
1149277 - Increase the Line-Height in Reader View from 1.44 rem to 1.6 rem
    FIXED in 40, uplifted to 39 and 38
1147889 - need transition when switching between light-dark-sepia
    FIXED in 39, uplifted to 38.
1137556 - Make the ReadingList sidebar look like other sidebars
    FIXED in 38
1146946 - TypeError: this.selectedItem is null from sidebar.js when using the up/down key when the list is empty.
    FIXED in 38
1150225 - Mouse cursor sticks to previous appearance from sidebar when over Reader View
    Toolkit-level bug, unlikely to be fixed by us.
    But, FIXED in 40.  \o/
1149073 - Transitioning the Font Size when changing Style in Reader View
    WONTFIX - too janky on low end machines.
Grand Master

The_Decryptor Veteran

Posted
  • Veteran
Posted

Thanks Webkit. /s

Funny thing is, when Microsoft first floated the idea of other engines parsing -webkit- CSS gunk, Apple was against it, worried they'd then have to support quirks in how other browsers parsed it.

Luckily for Apple, Microsoft and Mozilla actually care abut keeping their engines up to date and fixing bugs, so any parsing quirks will remain with WebKit.

Grand Master

The_Decryptor Veteran

Posted
  • Veteran
Posted

You can disable DRM support in the normal version, this build is special in that it's disabled at compile time, and the resulting support code isn't in the binary, so these builds can't even have it enabled at a later date without re-installing a normal version.

Edit: Quite a niche market though, due to how Mozilla has enabled the DRM modules to work all their code is completely open source, and can still be shipped with Linux distros (Even with DRM disabled by default). And considering how people actually liked when Google shipped their DRM support in Chrome for Linux, I doubt many people will complain.

Mentor

gohpep

Posted
Posted

You can disable DRM support in the normal version, this build is special in that it's disabled at compile time, and the resulting support code isn't in the binary, so these builds can't even have it enabled at a later date without re-installing a normal version.

Edit: Quite a niche market though, due to how Mozilla has enabled the DRM modules to work all their code is completely open source, and can still be shipped with Linux distros (Even with DRM disabled by default). And considering how people actually liked when Google shipped their DRM support in Chrome for Linux, I doubt many people will complain.

Yeah, I know, it is stated in the article that it is an option as well. These builds are programmed not to retrieve Adobe DRM player at all.

Experienced

tompkin

Posted
Posted

It requires the content provider to support the DRM first, and even then I think the client side support is still limited to YouTube playback.

Clues for the clueless: Why would Firefox be putting DRM support in it's browser? Who would want it?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing