Recommended Posts

i can understand why Australis dont look great in any Windoows Envirement but on Linux an MacOSX it looks good.

I dunno, looks pretty nice on my Windows desktop too, think my only real complaint would be nuking the add-on bar, that was just stupid. Can work around it mostly but there's one addon I use that hasn't been updated it, it only works in the add-on bar. But I'm sticking with beta, not in that build yet, only toying with nightly in a sandbox, hopefully things will even out by release.

 

it would be so much easier if it was in a TAB rather than a pop-up

There's a few addons that do that now -- Download Manager Tweak for example will let you have the downloads show up in a tab, sidebar or separate window.

All the in-content work is eventually going to transition that stuff to tabs anyway.

 

Didn't they make mockups for that as far back as version 4?  I don't know what channels to follow for this kind of info, so I'm curious why the extreme hold up.  16+ versions and one theme change later, and we're still waiting on things like downloads in a tab, etc.

Didn't they make mockups for that as far back as version 4?  I don't know what channels to follow for this kind of info, so I'm curious why the extreme hold up.  16+ versions and one theme change later, and we're still waiting on things like downloads in a tab, etc.

 

If you follow their BugZilla a little bit, you get a good view at how things work (or don't) at Mozilla. It takes them ages to implement something so all they really do is mockups. That is due to their "organizational" structure or however you want to call that. You get the feeling that noone really works there and just does a little work here, a little there, then a student project comes a long, re-does everything someone made but does not have time to finish so it sits there for months etc. It's horrible.

i aint been using Chrome for awhile now, its been unusable for awhile so i removed the package.

 

i can understand why Australis dont look great in any Windoows Envirement but on Linux an MacOSX it looks good. but there's no point whinging about it. its the way of the future. i see Loudnoise has stuck with the ESR, which is funny how these whinging people still use the Australis builds ( Nightly or Aurora ) . .

 

I have choices so I am not whining.. 

New things in Nightly:
 
HTML5 Canvas Hit testing support (only basic support landed - gained few points on html5test.com - although its behind preference "canvas.hitregions.enabled"): https://bugzilla.mozilla.org/show_bug.cgi?id=966591
Improving little performance of DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=976272 (it improved basically performance of this bug: (https://bugzilla.mozilla.org/show_bug.cgi?id=684305)
Moving Moz2D in libxul: https://bugzilla.mozilla.org/show_bug.cgi?id=976392 (If people here remember old PGO linker hitting limits on 32 bit) [Not landed but same: https://bugzilla.mozilla.org/show_bug.cgi?id=977701]
Oldie bug fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=401564
Golden Bug removing Main Thread I/O (quite big contender so now its down UI and Firefox will feel snappier for sure): https://bugzilla.mozilla.org/show_bug.cgi?id=975750
 
 
CSS GRID basic support is also landing soon behind preference.. Above mentioned bugs already landed.

Landed in mozilla-inbound:
Interesting No Audio bug on driver with vendor enhancement (more specifically SoundBlaster sound card): https://bugzilla.mozilla.org/show_bug.cgi?id=971693
CSS Blending bug fix with border-radius and overflow:hidden : https://bugzilla.mozilla.org/show_bug.cgi?id=952051
Native themeing for Help Button on Mac OS X: https://bugzilla.mozilla.org/show_bug.cgi?id=970079 (Image: https://bug970079.bugzilla.mozilla.org/attachment.cgi?id=8380796)
JS Debugger 2 related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=969786
Code cleanup (I don't know how much it affect Desktop but still Desktop share code base with Firefox OS so posting here): https://bugzilla.mozilla.org/show_bug.cgi?id=458300
CSS Transform Perspective + Box Shadow bug fix: https://bugzilla.mozilla.org/show_bug.cgi?id=970294
Rewrite of WebConsole API in C++ to take out about 3 different console API: https://bugzilla.mozilla.org/show_bug.cgi?id=965860
Eviction Algorithm for Media Source Extensions: https://bugzilla.mozilla.org/show_bug.cgi?id=976037

mix-blend-mode is still fairly buggy, I found a bad performance bug with it that is basically going to require it to be re-implemented :laugh:

 

Hahahahaha!!!!  :D  Efforts from start again!

Limited support for Pointer Events on non-metro environments landed in this nightly, not that useful without the support for the hardware (Like the Mac Touchpad), but at least Firefox now sends the correct events on those platforms, vs. nothing at all.

It's interesting that this type of support took so long, the whole point of Pointer Events was that it unified the existing mouse and touch APIs, so a single event is triggered regardless of the type of input, i.e. a mouse event is a pointer event. But until now Firefox only sent those events if you were running on something like a Surface, it wouldn't send any mouse only events even though the API supported it.

It's not like this support offers any extra functionality (It's literally just the same data as normal mouse events, but on a different object), but it reduces the amount of code pages have to write to support this "new" type of input (And here's hoping that OS X and Linux get full support soon enough, I want to try gestures out)

New things in Nightly:

 

HTML5 Canvas Hit testing support (only basic support landed - gained few points on html5test.com - although its behind preference "canvas.hitregions.enabled"): https://bugzilla.mozilla.org/show_bug.cgi?id=966591

Improving little performance of DOM: https://bugzilla.mozilla.org/show_bug.cgi?id=976272 (it improved basically performance of this bug: (https://bugzilla.mozilla.org/show_bug.cgi?id=684305)

Moving Moz2D in libxul: https://bugzilla.mozilla.org/show_bug.cgi?id=976392 (If people here remember old PGO linker hitting limits on 32 bit) [Not landed but same: https://bugzilla.mozilla.org/show_bug.cgi?id=977701]

Oldie bug fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=401564

Golden Bug removing Main Thread I/O (quite big contender so now its down UI and Firefox will feel snappier for sure): https://bugzilla.mozilla.org/show_bug.cgi?id=975750

 

 

CSS GRID basic support is also landing soon behind preference.. Above mentioned bugs already landed.

Landed in mozilla-inbound:

Interesting No Audio bug on driver with vendor enhancement (more specifically SoundBlaster sound card): https://bugzilla.mozilla.org/show_bug.cgi?id=971693

CSS Blending bug fix with border-radius and overflow:hidden : https://bugzilla.mozilla.org/show_bug.cgi?id=952051

Native themeing for Help Button on Mac OS X: https://bugzilla.mozilla.org/show_bug.cgi?id=970079 (Image: https://bug970079.bugzilla.mozilla.org/attachment.cgi?id=8380796)

JS Debugger 2 related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=969786

Code cleanup (I don't know how much it affect Desktop but still Desktop share code base with Firefox OS so posting here): https://bugzilla.mozilla.org/show_bug.cgi?id=458300

CSS Transform Perspective + Box Shadow bug fix: https://bugzilla.mozilla.org/show_bug.cgi?id=970294

Rewrite of WebConsole API in C++ to take out about 3 different console API: https://bugzilla.mozilla.org/show_bug.cgi?id=965860

Eviction Algorithm for Media Source Extensions: https://bugzilla.mozilla.org/show_bug.cgi?id=976037

Probably a dumb question, but the nightly updates that you mention, they apply to UX Nightly as well, right? If so, you said that Firefox will feel snappier. How so? Lower memory usage, more responsive UI, etc?

Probably a dumb question, but the nightly updates that you mention, they apply to UX Nightly as well, right? If so, you said that Firefox will feel snappier. How so? Lower memory usage, more responsive UI, etc?

It depends on how often they merge the main codebase into the UX branch 9They probably do it every few days, so you'll be behind a bit)

And the "snappier" stuff really depends on what type of computer you have, my PC is pretty good so the snappy work hasn't had any effect (A 2fps increase from 58 to 60 is pretty much noise, while from 2fps to 4fps is doubling performance, etc.)

Probably a dumb question, but the nightly updates that you mention, they apply to UX Nightly as well, right? If so, you said that Firefox will feel snappier. How so? Lower memory usage, more responsive UI, etc?

 

Firefox is single threaded and all process run on main thread and all processes are run in queue, if one bottleneck from main thread is gone, it surely feels smoother and sometime improve performance throughout. (Many stuff and processes has been taken down and run in off the main thread now and it is continuous work even after electrolysis lands since they need to move process still then to other process).

The main thread I/O gone above is related to HTTP Debug code use to measure stuff, its was taken out now. So every connection does not has its overhead now.

Guys, the Metro version of Nightly doesn't work. Even on clean install Windows 8.1

 

Resolution: 1680x1050

CPU: Intel Core 2 Quad Q6600

RAM: 3GB(lame frequencies)

 

Latest Nightly version.

 

It shows the full-screen Nightly Metro logo and then closes by itself. On Task Manager I see that it opens, uses around 35mb of RAM and closes.

 

 

Not that I care, but I want to have it as an option. I guess Mozilla coders are kind of lame.(can give some examples but not in the mood, so if possible, do not comment on this, just help me with my problem)

Firefox is single threaded and all process run on main thread and all processes are run in queue, if one bottleneck from main thread is gone, it surely feels smoother and sometime improve performance throughout. (Many stuff and processes has been taken down and run in off the main thread now and it is continuous work even after electrolysis lands since they need to move process still then to other process).

The main thread I/O gone above is related to HTTP Debug code use to measure stuff, its was taken out now. So every connection does not has its overhead now.

There's a rather early implementation of electrolysis in the nightly builds at the moment, only works on platforms where the rendering has been separated onto another thread though (So, not Windows)

File > New e10s Window

There's a rather early implementation of electrolysis in the nightly builds at the moment, only works on platforms where the rendering has been separated onto another thread though (So, not Windows)

File > New e10s Window

 

I already know but I deliberately not mentioned it because its buggier and if he tried he might be little disappointed.

Firefox is single threaded and all process run on main thread and all processes are run in queue, if one bottleneck from main thread is gone, it surely feels smoother and sometime improve performance throughout. (Many stuff and processes has been taken down and run in off the main thread now and it is continuous work even after electrolysis lands since they need to move process still then to other process).

The main thread I/O gone above is related to HTTP Debug code use to measure stuff, its was taken out now. So every connection does not has its overhead now.

Good to know. Thanks!

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