updates Meet the browser: Firefox Next

[indospot Veteran]

I wish they at least made it a separate release from the current.

[Pikey]

Tabs crashing almost constantly here, turning off the 'multi-process Nightly' fixes it though.

 

Meanwhile this threads gone real quiet ... ?

[The_Decryptor Veteran]

Nothing's really happened

There's been a bunch of UI and feature work for the 10 release (Like if Firefox is the default browser and you do a search through Cortana, it'll pull out the search string and run that via your default search engine and not just Bing). I've been following the media work a bit and there's been some big changes, but it's all low level architectural crap that isn't very interesting to normal people

Edit: Oh yeah, a bunch of work on APZ, both for desktop and the Android release (See ya Java APZ), and they're slowly moving the Linux release off GTK2/X11 to GTK3/Cairo (or Skia) that will eventually allow for native Wayland rendering (And in the short term greatly improve HiDPI rendering on Linux). Font support has been improved on Linux too, but due to how some distros do things that's constantly running into issues.

[remixedcat]

anyone finding the fonts not so great for the latest waterfox version? I've had to force candara since the defaults are hella jaggy

[bawz]

https://wiki.mozilla.org/Firefox/Go_Faster

 

so what there gonna do is, make " Hello " as a permanent Addon. you wont be able to uninstall it but you'll be able to Disable it.

 

http://forums.mozillazine.org/viewtopic.php?f=7&t=2947865

[The_Decryptor Veteran]

Latest OS X nightly has APZ enabled, and either tonight's or tomorrows should have it enabled on Windows as well.

Edit: Oh yeah, looks like the OS X release is going to move from CoreGraphics for rendering to Skia, since in some workloads Skia is stupidly faster (Like 200x faster)

[BooBerry]

Microsoft ship a WebDriver implementation

 

Firefox nightlies for Linux are now using Gtk+3

[bawz]

in that Bug mentioned, gtk2 code should be removed as it isnt compatible or doesnt work in Wayland, whereas GTK3 does

[ViperAFK]

Latest OS X nightly has APZ enabled, and either tonight's or tomorrows should have it enabled on Windows as well.

Edit: Oh yeah, looks like the OS X release is going to move from CoreGraphics for rendering to Skia, since in some workloads Skia is stupidly faster (Like 200x faster)

good to hear, APZ makes a MASSIVE improvement in scrolling on the osx version. I just really hope they fix this soon: https://bugzilla.mozilla.org/show_bug.cgi?id=1016035

[The_Decryptor Veteran]

in that Bug mentioned, gtk2 code should be removed as it isnt compatible or doesnt work in Wayland, whereas GTK3 does

 

GTK3 helps with Wayland support, but doesn't itself let you render via Wayland. Gecko still relies heavily on X11 for a lot of things (Like all page rendering), and while they're moving away from it, it still takes time (And it might piggyback off the OS X porting work, since they want to use Skia for both platforms, and for fallback on Windows in the future).

 

good to hear, APZ makes a MASSIVE improvement in scrolling on the osx version. I just really hope they fix this soon: https://bugzilla.mozilla.org/show_bug.cgi?id=1016035

I don't mind the lack of gestures, but yeah the smoother scrolling is nice to have. The work on the mobile variant is coming along nicely too, the way the Android version behaves is quite buggy (Funny, because it's the original APZ implementation that was forked for B2G work, which improved it so much that the original version feels broken in comparison)

[rsnn]

Mozilla to release 64-bit Firefox to stable channel in version 41

[Boo Berry]

Mozilla to release 64-bit Firefox to stable channel in version 41

 

Well, that's good...

[bawz]

Mozilla to release 64-bit Firefox to stable channel in version 41

it'll be 42 next . it was supposed to be FF40, now 41,

[The_Decryptor Veteran]

Audio indicators on tabs has landed

Tab widths could probably stand to be a bit larger to accommodate it.

[bawz]

Audio indicators on tabs has landed

Tab widths could probably stand to be a bit larger to accommodate it.

hopefully there's a way to Disable that rediculous feature

[.stan]

hopefully there's a way to Disable that rediculous feature

What, why? That's super useful..

[Boo Berry]

Indeed, I find myself using it a lot in Chrome and Edge right now. I was just thinking yesterday about Firefox's lack of it.

[bawz]

What, why? That's super useful..

might be for some that spend there entire time on Youtube type pages, i dont

[The_Decryptor Veteran]

might be for some that spend there entire time on Youtube type pages, i dont

Good thing there's no such thing as ads that automatically play sound right.

[Ryoken]

might be for some that spend there entire time on Youtube type pages, i dont

All it does is tell you what tabs are making sound.. Maybe you don't ever have the issue of auto-playing adverts or videos, but feeling the need to go disable it.. really?

[bawz]

All it does is tell you what tabs are making sound.. Maybe you don't ever have the issue of auto-playing adverts or videos, but feeling the need to go disable it.. really?

i pretty much use ublock origin to block that crap. . i do use websites that auto-play Vids but i thought you could stop that by telling Flash to " Ask To Activate . "  or you could use the Extension "  FlashBlock "

[+Red King Subscriber²]

Audio indicators on tabs has landed

Tab widths could probably stand to be a bit larger to accommodate it.

Well that is straight from Chrome

[torrentthief]

i pretty much use ublock origin to block that crap. . i do use websites that auto-play Vids but i thought you could stop that by telling Flash to " Ask To Activate . "  or you could use the Extension "  FlashBlock "

some autoplaying ads use html5 nowadays, there is no way to stop those at the moment with extensions.

[bawz]

some autoplaying ads use html5 nowadays, there is no way to stop those at the moment with extensions.

thats true, i didnt think bout that

[The_Decryptor Veteran]

Well that is straight from Chrome

Can we stop doing this over every single feature that multiple browsers implement? Safari, Opera and Edge all do the same thing.