updates Meet the browser: Firefox Next

[bogas04]

Have a look here : http://arewefastyet.com/?a=b&view=regress

:D

[The_Decryptor Veteran]

Acording to the heat map (https://blog.mozilla...results-are-in/), the panorama is least being used. They should kill panorama and restore standard windows frames because it is a big problem for taking screenshots of long pages with third party tools.

Panorama is the least used because it's hidden by default, if you don't know the key combo (or hit it by accident) or add it to the toolbar manually, you won't ever see it.

And restoring the window frames won't do anything since the actual issue you're talking about is the lack of child windows, they dropped that for hardware acceleration (IE uses child windows, and only they're accelerated, Firefox doesn't and the entire UI is accelerated)

[+Nexus18 MVC]

Not liking the australis look at all!

Are there any good themes or userstyles that I can apply to get the old look back or something better at least?

[Syanide]

Once they get rid of the Menu button, it's going to be virtually indistinguishable from Chrome.

[articuno1au]

You could make it look exactly like Chrome if you wanted

FXChrome is the theme I'm using >.<

I'm using a ton of other things to make it identical to Chrome (like the context menus and stuff) but appearance wise, that's all you need.

[+Nexus18 MVC]

Yeah going to get the proper chrome look like yours now arti.

Australis still needs a lot of work IMO.

How do I disable the add on compatibility check? Trying to install FX-chrome but it says it is incompatible with with firefox V16.

[ArialBlue]

Please inform me when there is a way to get rid of rounded tabs.

[+Nexus18 MVC]

Ignore my last post....

[bogas04]

Not liking Australis Design? Want to tell developers how it is a bad idea?

Post it here http://twitter.com/MozillaUX :)

Trust me if they get like tonnes of people saying it is bad idea , they will rethink for sure

On other hand , Ion is now very close to the performance of JM+TI (14% faster in Kraken , 13% slower in SS , 12.2% slower in v8 )

[bogas04]

New InContent preferences with vertical category list try builds are out , this is how it looks :

[Kirkburn]

Once they get rid of the Menu button, it's going to be virtually indistinguishable from Chrome.

http://people.mozill...ckup-panel.html does not include removal of the menu button.

If you check the toolbar menu, it does not include a lot of stuff that's on the menu button. Accordingly, I don't think the menu button is going away.

(Besides, I fail to understand why tab shapes have to be different ... just to be different.)

[+Gary7 Subscriber²]

^ Because everyone can't copy chrome.

[The_Decryptor Veteran]

http://people.mozill...ckup-panel.html does not include removal of the menu button.

If you check the toolbar menu, it does not include a lot of stuff that's on the menu button. Accordingly, I don't think the menu button is going away.

(Besides, I fail to understand why tab shapes have to be different ... just to be different.)

I'm not a fan of the new tab design, mainly because I think they're too big. I don't like the similar design in Chrome either.

The tabs work in fennec, because it's designed for a touch screen, stuff needs to be big there.

[Kaoxt]

http://people.mozill...ckup-panel.html does not include removal of the menu button.

If you check the toolbar menu, it does not include a lot of stuff that's on the menu button. Accordingly, I don't think the menu button is going away.

(Besides, I fail to understand why tab shapes have to be different ... just to be different.)

That is a very old mockup. It's from September 2011. The one below is from February 2012. If you notice it still has the forward/back button combination and the toolbar buttons have borders. The menu button is moving to the right side, which is why he said it will be hard to tell the difference between Firefox and Chrome. Expect it to look more like this:

Interactive demo: https://people.mozil...mainWindow.html

Mozilla wants to unify their applications. Firefox / Thunderbird will both look very similar.

[bogas04]

In the end all Non IE browsers except Safari look all same :p Let's stop this that they are copying or are exactly like Chrome, the thing is , is Firefox's implementation better? And for that , let's wait for it to completely implement :)

[+Zlip792 MVC]

In the end all Non IE browsers except Safari look all same :p Let's stop this that they are copying or are exactly like Chrome, the thing is , is Firefox's implementation better? And for that , let's wait for it to completely implement :)

Safari is still looking like same as before. IE also evolved it from IE6 to IE7 and then little bit in IE8 and overhauled in IE9.

Firefox is doing really medoicre job.

You have to agree that current UI can be made responsive by fixing recent three filed bugs related to poor hardware acceleration cases which affect UI a lot and by Super Snappy then why forcing people to some crap like Australis.

Unification is good thing when you have resource power like many workforce which Google has, in case of Firefox slowly improving and not making their loyal users angry is best bet. Even now I left Nightly completely, only using Chromium 21 and sometime Opera 12. Opera has many limitation which resulted to not make it my default browser even if it has 64-bit browser now.

I am quite pleased with development in Firefox 15 and I was hoping that it could do better job in future since now ground basis of it is now strong but ....

[LAMj]

...

Firefox is doing really medoicre job.

...

They are doing a pretty horrible job actually. I still have a portable version of Firefox 3.6 that I use sometime. And what I notice is that FF3.6 ui actually feel quicker. For example loading 10+ tabs at the same time, FF3.6 UI is still responsive. On the other hand when I load 10+ tabs in FF13, the ui is noticeably unresponsive for a few seconds.

When your new version is performing slower than an ancient version, there's definitely something Mozilla is not doing right.

[+Zlip792 MVC]

They are doing a pretty horrible job actually. I still have a portable version of Firefox 3.6 that I use sometime. And what I notice is that FF3.6 ui actually feel quicker. For example loading 10+ tabs at the same time, FF3.6 UI is still responsive. On the other hand when I load 10+ tabs in FF13, the ui is noticeably unresponsive for a few seconds.

When your new version is performing slower than an ancient version, there's definitely something Mozilla is not doing right.

Quite agree with you, I am using Firefox since FF2 (even before that to be exact).. and they did poor job after going with Asa decision of rapid release cycle and then doing some half baked jobs like currently Ion Monkey making them separate and much better, fooled merged them with old engine for hot loops calculations, good things not happen in second they should think and work for longer but better stuff. There one mistake is when they can update Cairo to latest why waiting for several years for Azure API.. New Cairo API can brings several speedup across browser. Even currently Azure API use Cairo API as a backend on Windows..

Its bug is stale mode from many weeks.

[Kyang]

Latest nightly, Aero snap, and YouTube. Anyone else unable to drag the window down from maximized? When I try to, the window just snaps right back up.

Sometimes, when the page first loads, the drag down works. Second time though, it fails, and every time after that.

EDIT:

Seems like the Aero Snap still works when first switching to a tab with the flash content on it. But if the tab stays in focus, then subsequent attempts to use Aero snap do not work, at least until the user switches back and forth to another tab then back again.

[dysgenics]

seems they backed out the curved tabs in UX?

[Kirkburn]

That is a very old mockup. It's from September 2011.

Ah, thanks. (Someone linked it as being new earlier)

[ArialBlue]

seems they backed out the curved tabs in UX?

Let us have hope.

[+Gary7 Subscriber²]

Quite agree with you, I am using Firefox since FF2 (even before that to be exact).. and they did poor job after going with Asa decision of rapid release cycle and then doing some half baked jobs like currently Ion Monkey making them separate and much better, fooled merged them with old engine for hot loops calculations, good things not happen in second they should think and work for longer but better stuff. There one mistake is when they can update Cairo to latest why waiting for several years for Azure API.. New Cairo API can brings several speedup across browser. Even currently Azure API use Cairo API as a backend on Windows..

Its bug is stale mode from many weeks.

I have been using Firefox since it was Phoenix and to me Mozilla has gone mad.

[Kaoxt]

Ah, thanks. (Someone linked it as being new earlier)

No problem! :)

[The_Decryptor Veteran]

Quite agree with you, I am using Firefox since FF2 (even before that to be exact).. and they did poor job after going with Asa decision of rapid release cycle and then doing some half baked jobs like currently Ion Monkey making them separate and much better, fooled merged them with old engine for hot loops calculations, good things not happen in second they should think and work for longer but better stuff. There one mistake is when they can update Cairo to latest why waiting for several years for Azure API.. New Cairo API can brings several speedup across browser. Even currently Azure API use Cairo API as a backend on Windows..

Its bug is stale mode from many weeks.

Do you know the differences between Azure and Cairo? Do you know why they're using one over another?