updates Meet the browser: Firefox Next

[+Zlip792 MVC]

I'm getting really sick of this ridiculous hyperbole that a new theme will make firefox "crap". Its the silliest thing I have ever heard. Do you just use firefox for the theme?

Reduced functionality???? Huh!!!!

 

I used Australis UX builds as well but came across same thinking it is lacking one way or another + thousands and gazillion times in this thread told  that each has his own preferences and freedom of speech... Which I use.

[bawz]

The issue is that if they roll it out, after that if they have to backout, even previous theme will not work as working currently, means totally useless. To fix it up, they either have to maintain two separate branches which was proposed like Australis + mozilla central and mozilla central simple without Australis, so that if some mess up happen, they can roll out other one.

 

But they think that delaying it further to fix more issues like now it is on Milestone 8, previously it was thought to roll out on achieving Milestone 7. So they are fixing more and more bugs.

 

From my side, in one sentences, what is worthless will remain worthless, Australis is crap and with it Firefox will become crap.

 

You can witness this happening with new useless Click to Play.

i dont mind the Austeralis Tabs, but thats all, click-to-play  has been useless from Day 1. same with Panarama useless feature. 

[vcfan]

i used to love firefox,back in the  <= ie8 days,but then ie became awesome,and firefox became bloated.

[ViperAFK]

i used to love firefox,back in the  <= ie8 days,but then ie became awesome,and firefox became bloated.

Firefox's performance has been consistently improving, its certainly not anymore "bloated" than IE.

 

I'm getting really sick of this thread, its become the 'make moronic flamebait posts about firefox thread'.

 

The first post in this thread says: Thread discussing feature landings and bugs etc in Pre-Release Builds of Firefox

 

Not the make trollish comments an discuss the merits of other browser's thread.

[vcfan]

Firefox's performance has been consistently improving, its certainly not anymore "bloated" than IE.

 

I'm getting really sick of this thread, its become the 'make moronic flamebait posts about firefox thread'.

 

The first post in this thread says: Thread discussing feature landings and bugs etc in Pre-Release Builds of Firefox

 

Not the make trollish comments an discuss the merits of other browser's thread.

i never said i dont like firefox,in fact i have the latest version installed use it mostly for backup if some site misbehaves in ie. geez calm down.

[Konstantine]

I'm using UX for over a month now, and the new theme is both amazing and beautiful. I don't get it why you don't like it.

[cetla]

@Zlip.

 

What's wrong with click-to-play? Are you refering to the plugins stuff? I have it enabled actually. Eliminate all the flash exploits and trackers.

 

But I agree with you, Australis is utter crap. It will make Mozilla's incompetent Gecko engine even more crappy. I hope it remains in development hell forever.

[+Zlip792 MVC]

@Zlip.

 

What's wrong with click-to-play? Are you refering to the plugins stuff? I have it enabled actually. Eliminate all the flash exploits and trackers.

 

But I agree with you, Australis is utter crap. It will make Mozilla's incompetent Gecko engine even more crappy. I hope it remains in development hell forever.

 

Actually issue with click to play is that its icon is very confusing and irritating and its on global per site basis rather than per element on site basis like other addons do.

For those people asking about eletcrolysis thingy, it is being worked on in this branch: https://hg.mozilla.org/projects/larch/shortlog

 

And you can find larch branch builds from here (Windows 32-bit): https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/larch-win32/

[ViperAFK]

@Zlip.

 

What's wrong with click-to-play? Are you refering to the plugins stuff? I have it enabled actually. Eliminate all the flash exploits and trackers.

 

But I agree with you, Australis is utter crap. It will make Mozilla's incompetent Gecko engine even more crappy. I hope it remains in development hell forever.

Gecko is hardly a crappy or incompetent engine, and how on earth will a different firefox UI make the engine crappy? Do people realize how ridiculous the stupid **** they keep saying in this thread sounds?

 

There was a time where this thread had interesting discussion, but now everytime I see a new post in this thread and click on it its one of these silly troll-comments.

[The_Decryptor Veteran]

The issue is that if they roll it out, after that if they have to backout, even previous theme will not work as working currently, means totally useless. To fix it up, they either have to maintain two separate branches which was proposed like Australis + mozilla central and mozilla central simple without Australis, so that if some mess up happen, they can roll out other one.

...

I'm not entirely sure what this means, but if you mean that they can't land a feature, work on it and then back it out then no, they can easily do that.

It's kinda the whole point of source control systems.

[+Zlip792 MVC]

I'm not entirely sure what this means, but if you mean that they can't land a feature, work on it and then back it out then no, they can easily do that.

It's kinda the whole point of source control systems.

 

 

LOL!! They mentioned this excuse not made by me....

[+Zlip792 MVC]

Good news for people pointing fingers toward Firefox UI responsiveness:

Unofficial comment quoting from bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=899338

 

Right now we've worked around the backspace handling problem in the larch repo by deleting the command that calls BrowserHandleBackspace(). However, it's still a problem on mozilla-central. This patch does pretty much the same thing, but it only disables the command when gMultiProcessBrowsing is set.

 

Obviously we'd like to fix this the right way in the future. However, we're trying to make m-c usable for multiprocess browsing by mid-August.

[Yogurtmaster]

Firefox is the new Netscape. It's slow, crashes easily, the page rendering is still old fashioned, webGL is slow, html5 is slow.

I still use Firefox every once in a blue moon, but it's a mess in my opinion.

[bawz]

Firefox is the new Netscape. It's slow, crashes easily, the page rendering is still old fashioned, webGL is slow, html5 is slow.

I still use Firefox every once in a blue moon, but it's a mess in my opinion.

saying WebGL an HTML5 slow is a bit premature . yes Gecko is Old thats why there working on Servo to replace Gecko.  . how is Firefox a Mess?

[Yogurtmaster]

saying WebGL an HTML5 slow is a bit premature . yes Gecko is Old thats why there working on Servo to replace Gecko.  . how is Firefox a Mess?

So they are going to use hardware acceleration instead of the typical old school CPU? I normally use Chrome because FireFox always crashes on certain pages of HTML and the rendering of pages isn't good.

I am waiting on IE 11 as that seems like the best option. Sure it doesn't use plugins but I don't use any plugins for FireFox or Chrome.

If Firefox stops crashing on viewing my email account and if it renders to the screen in higher quality fonts and if it accelerates all of the HTML5/graphics/webGL pipeline then I might have another look. I have fallen in Love with IE 11 and I haven't used IE since IE 7 or 8.

[The_Decryptor Veteran]

What?

Firefox has used the GPU since 4.0, and IE11 supports plugins (And if you mean addons, well IE supports those as well)

[ViperAFK]

Firefox is the new Netscape. It's slow, crashes easily, the page rendering is still old fashioned, webGL is slow, html5 is slow.

I still use Firefox every once in a blue moon, but it's a mess in my opinion.

 

So they are going to use hardware acceleration instead of the typical old school CPU? I normally use Chrome because FireFox always crashes on certain pages of HTML and the rendering of pages isn't good.

 

 

 

1. I can't remember the last time firefox crashed on me, nor can I remember the last time I had page rendering/site compatibility issues, and I use it on many computers and multiple operating systems, you are most likely running into some sort of bug that is certainly not 'normal behavior'. What site(s) is it crashing on? Why haven't you reported a bug?

 

How the hell is page rendering "old fashioned"? That doesn't even make any sense.

 

2. Firefox has hardware acceleration, and has for a long time. Firefox supports directx hardware acceleration, d2d, and directwrite like IE does.

 

And firefox's performance holds up pretty well these days: http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-12.html

[cetla]

@above

I couldn't get through a day without Firefox crashing at least once...just moments ago Firefox went kaput while browsing on Jolidrive. Firefox tendency to crash on web apps is pretty frequent for me. It just can't handle complex DOM pages. Also DOM event funtions is poorly handled. As I've argued before, Gecko is getting old and incompetent.

 

Mozilla focused too much on the javascript side of thing and neglected its renderer--which I think is much more important to the end user. Just look at IE, its Chakra javascript is not as fast as Firefox's, but its Trident renderer is much more stable at handling web apps. Chrome Webkit-fork is the same.

[Yogurtmaster]

1. I can't remember the last time firefox crashed on me, nor can I remember the last time I had page rendering/site compatibility issues, and I use it on many computers and multiple operating systems, you are most likely running into some sort of bug that is certainly not 'normal behavior'. What site(s) is it crashing on? Why haven't you reported a bug?

 

How the hell is page rendering "old fashioned"? That doesn't even make any sense.

 

2. Firefox has hardware acceleration, and has for a long time. Firefox supports directx hardware acceleration, d2d, and directwrite like IE does.

 

And firefox's performance holds up pretty well these days: http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-12.html

I have Firefox 22 and it's much slower than Chrome at many things and both are slower than IE 11 by oh a heck of a lot. I have all of the latest versions of browsers and my Nvidia drivers are the latest non beta as well and Firefox is slower and it also renders worse than IE 11. No doubt about it. It's not even up for debate.

Believe me, I am not a fan of IE at all. I just tried it on Windows 8.1 in a VM of all places and I can instantly tell a difference easily. I know that's not an easy thing to hear, but it is so true. I also used to have to zoom in to see the fonts on my web browsers, but IE 11 renders them so much better, that I don't have to zoom in anymore. I was completely blown away by it. The last IE I really used was 8 and then I switched to Firefox and then on to Chrome as Chrome kept getting better over time. When Windows 8.1 came out with the public release I tried IE 11 and I couldn't believe how far it has come. It makes the other browsers look like crap.

[sao123]

Firefox will never compete with other browsers until it has seperately threaded downloads...

 

When I close the main window because I am done viewing an HTML page... that doesnt mean my downloads in progress should also stop and close...

NO.  They should continue into the background until they complete.

[The_Decryptor Veteran]

@above

I couldn't get through a day without Firefox crashing at least once...just moments ago Firefox went kaput while browsing on Jolidrive. Firefox tendency to crash on web apps is pretty frequent for me. It just can't handle complex DOM pages. Also DOM event funtions is poorly handled. As I've argued before, Gecko is getting old and incompetent.

 

Mozilla focused too much on the javascript side of thing and neglected its renderer--which I think is much more important to the end user. Just look at IE, its Chakra javascript is not as fast as Firefox's, but its Trident renderer is much more stable at handling web apps. Chrome Webkit-fork is the same.

Check what other plugins/extensions/etc. you have loaded into Firefox, crashing daily is a sign you've got something else wrong.

Firefox is fine at handling events, it's fine at rendering pages, etc.

Edit: I exclusively run the nightly version on my Mac, and I've only crashed once in the last month (due to an OOM issue with OpenGL)

[+Zlip792 MVC]

Firefox thumbnail services now also use Electrolysis which means using background thread to update after certain time.

https://groups.google.com/forum/#!topic/mozilla.dev.platform/2WHROKmyQso

[The_Decryptor Veteran]

The next nightly on OS X will have support for a font-smoothing property similar to WebKit (Called -moz-osx-font-smoothing to make it clear it's Mac only).

Authors wanted it for various reasons, ranging from "Well I like it so the user has to see it" to "This hack I'm using needs it and I won't consider using a better method", but luckily Mozilla included a preference to disable support for the CSS property, so toggling "layout.css.osx-font-smoothing.enabled" to "false" means Firefox will respect your settings over the authors opinion.

[ViperAFK]

@above

I couldn't get through a day without Firefox crashing at least once...just moments ago Firefox went kaput while browsing on Jolidrive. Firefox tendency to crash on web apps is pretty frequent for me. It just can't handle complex DOM pages. Also DOM event funtions is poorly handled. As I've argued before, Gecko is getting old and incompetent.

 

Mozilla focused too much on the javascript side of thing and neglected its renderer--which I think is much more important to the end user. Just look at IE, its Chakra javascript is not as fast as Firefox's, but its Trident renderer is much more stable at handling web apps. Chrome Webkit-fork is the same.

People keep making this weird claim about firefox's "renderer being bad" but with little to back it up. I never have any problems with firefox's rendering of pages, nor have I had any stability issues with it... I just created a jolidrive account and browsed around in it for quite a while, I can't get it to crash at all here. I also use webapps such as google docs and skydrive pretty frequently, never have any issues on my machines. If you are getting crashes you should probably report a bug.

[cetla]

People keep making this weird claim about firefox's "renderer being bad" but with little to back it up. I never have any problems with firefox's rendering of pages, nor have I had any stability issues with it... I just created a jolidrive account and browsed around in it for quite a while, I can't get it to crash at all here. I also use webapps such as google docs and skydrive pretty frequently, never have any issues on my machines. If you are getting crashes you should probably report a bug.

 

Weird claim? I'm just reporting what works and doesn't with Firefox on my end.

 

My claim of Firefox doesn't handle web apps is pretty grounded. Since you just signed up for Jolidrive, go ahead and test its music player. There's a bug with the seeker and volume slider in Firefox. You can't manipulate them. Works fine in Chrome and IE10.

 

I also check the crashdump I had early on Jolidrive, apparently Firefox is cocking up with mp3 playback. Most music/radio sites have Flash fallback for handling mp3s (specifically for Firefox) but Jolidrive doesn't so it crashed for god knows what reason...