updates Meet the browser: Firefox Next

[Rappy Veteran]

The recent Nightly update is awful :/

[+Zlip792 MVC]

The recent Nightly update is awful :/

 

In which way? Right click context menu? Australis? OMTC Regressions? Irregex regression?

[Rappy Veteran]

In which way? Right click context menu? Australis? OMTC Regressions? Irregex regression?

 

Context Menu and the loading animation in the tab is kinda ######ed

[+Zlip792 MVC]

Context Menu and the loading animation in the tab is kinda ######ed

 

Context Menu changes are experimental and it will change a lot in future, you should read PDF attached in its bug for future prospect of it.

Here its link for PDF direct: https://bug1000513.bugzilla.mozilla.org/attachment.cgi?id=8411345 ; Blog post on Context Menu: http://msujaws.wordpress.com/2014/05/27/experimenting-with-context-menus/

As for loading animation in the tab, bug has been filed, I think it will take few days maximum I think. Actually merge day is coming near, so they will now focus on fixing regressions rather than landing big chunk changes.

[Rappy Veteran]

Context Menu changes are experimental and it will change a lot in future, you should read PDF attached in its bug for future prospect of it.

As for loading animation in the tab, bug has been filed, I think it will take few days maximum I think. Actually merge day is coming near, so they will now focus on fixing regressions rather than landing big chunk changes.

 

I could get used to context menu, just seems weird atm

[+Zlip792 MVC]

I could get used to context menu, just seems weird atm

 

Indeed but you will admit that its way much better than IE11 which has awful right click context menu which includes disabled states as well in it and many other stuff as well..

Is this what you are facing with tab loading animation:

http://screencast.com/t/fViRLzExHEh

[The_Decryptor Veteran]

It looks like they changed the loading throbber to be a static element that's animated (vs. an animated picture), but you get sampling artifacts that leads to black marks on the edges.

At least that's what I'm seeing.

[Rappy Veteran]

Indeed but you will admit that its way much better than IE11 which has awful right click context menu which includes disabled states as well in it and many other stuff as well..

Is this what you are facing with tab loading animation:

http://screencast.com/t/fViRLzExHEh

 

Yeah it is, just looks a bit weird

[+Neyht Subscriber²]

Is there a way for Firefox on the Mac to, for instance, not maximize the images in the Desktop Showcase threads on this site? It goes against how Safari and Google Chrome handles these images - they appear maximised in Firefox but inline images are cut off on the right hand side. I looked in about:config for the automatic image resize setting and that was already set to true. Google'ing turned up nothing with regards to this other a post suggesting to turn off automatic resizing for images.

 

Is this a question that has been asked before and problem solved? 

 

Any idea as to what I'm talking about?

 

I would say to post it on site and forum issues but this has got to be known already.  It probably works this way for a reason.

[The_Decryptor Veteran]

Toggling image resizing in about:config won't have any effect, that only applies to standalone images.

The proper behaviour here is apparently undefined, Firefox and IE render it one way, Chrome and Safari another. Personally I think WebKit/Blink is wrong here though (The image is being told to fit the parent element, and the parent element is being told to fit the image, Firefox and IE fit it to the image, WebKit/Blink instead fits it to the parent element of the images parent element.)

[Rappy Veteran]

Is this what you are facing with tab loading animation:

http://screencast.com/t/fViRLzExHEh

Fixed :D

[+Red King Subscriber²]

Indeed but you will admit that its way much better than IE11 which has awful right click context menu which includes disabled states as well in it and many other stuff as well..

Is this what you are facing with tab loading animation:

http://screencast.com/t/fViRLzExHEh

Go home Firefox you're drunk.

[ViperAFK]

This looks interesting, looks like there is some movement on implementing APZC for the mac version, if I understand correctly this could significantly improve scrolling responsiveness: https://bugzilla.mozilla.org/show_bug.cgi?id=944938

 

APZC + Tiled layers is what would be equivalent to OSX's 'responsive scrolling'.

[The_Decryptor Veteran]

APZC and tiling is what's used in the Android version (And everywhere with Chrome), it'll provide much better responsiveness than what's currently implemented (At the moment every scroll requires a repaint of the newly shown contents, with tiling the browser renders more than what's visible, but then you can scroll anywhere within that visible region without repainting)

It'll work better with multi-process tabs too, instead of the tab processes repainting when the parent scrolls, they can just go to sleep and never do any work.

[.stan]

And Mozilla finally feeling the need to move on with their 64bit plans as well https://groups.google.com/forum/#!msg/mozilla.dev.platform/oB-GAXt6Ijo/lUgjfUZ8ArEJ

[The_Decryptor Veteran]

I've been saying for ages that 64bit wasn't important because all it really offered was extra RAM availability (And I've only ever seen one person who was actually hitting that), but it seems with Windows 8 (or 8.1) Microsoft added a new, more secure form of ASLR that both requires a 64bit app, and requires the app to try to take advantage of the 64bit address space. I think that's a good enough reason honestly, actually adds a benefit for end users.

The overwhelming majority of Internet users could neither tell you what 64 bit means, nor will they have seen Google's announcement.

He's right about the first part, probably not the second. Most people have no idea what 64bit is (Or offers), but I think a bunch are going to see Google's announcement, have no idea what it means, but get the idea that Chrome is better because of it (Ignoring that even IE6 was available as a 64bit release)

Although I do find it funny how in the span of a few years we've gone from "Firefox uses 500MB of RAM, what a memory hog!" to "Firefox can only use 4GB of RAM? That's outdated!"

[The_Decryptor Veteran]

So with a new OS X theme comes a new revision to Australis, not sure how I feel about it, but it is just a mockup (And it does fit the OS theme, which might be half the problem)

[Menge]

So with a new OS X theme comes a new revision to Australis, not sure how I feel about it, but it is just a mockup (And it does fit the OS theme, which might be half the problem)

 

One tiny little nitpick I have with this mockup is that in Yosemite titlebars are transparent to the content of the window, and sidebars are transparent to the background. This mockup has a titlebar transparent to the desktop, which would be inconsistent.

 

And I totally approve of everyone going 64-bit. A regular user would not know what memory protection is, but we all know how useful that was over the last decade or so :)

[Lamp0]

That's not an offcial mockup though is it? As I understand it Yosemite removes the Fullscreen button on the right.

[The_Decryptor Veteran]

It's an "official" mockup, it's not a prototype or anything so the OS isn't actually involved.

I don't actually have Yosemite, so what does it do with the fullscreen button?

[+Frank B. Subscriber²]

It's an "official" mockup, it's not a prototype or anything so the OS isn't actually involved.

I don't actually have Yosemite, so what does it do with the fullscreen button?

The green 'traffic light' button fullscreens an app rather than use the previous 'zoom' feature.

[The_Decryptor Veteran]

Oh that's going to annoy me.

[Guest]

I have, actually. Still happens. I'll play with it for a bit, try to uninstall, remove everything FF-related, then reinstall to see if that fixes the problem. Thank you all for the replies!

 

Seems to have been fixed in the latest version.

[Lamp0]

Oh that's going to annoy me.

 

yea, I figured they could have a right click on green be a zoom feature or something.

[+Zlip792 MVC]

-- In-Content UI is disabled for Firefox 32.

-- YARR (Yet Another Regular Expression) code ported from Webkit has been removed from m-c (mozilla central) code base and Irregexp (from v8) replaced YARR.

-- After shifting to mozilla::pikx certificate validation, devs are planning to rip out NSS based code from M33.

-- Currently UTF-16 and ASCII strings conversion to UTF-8 is happening in mozilla JS side, it will improve performance and memory usage. v8 engine of Chrome already do this. Its Latin1 strings project.

 

Landed on mozilla-inbound

-- MemShrink P1 (Javascript) [Consolidate ScriptSources with the same source] - https://bugzilla.mozilla.org/show_bug.cgi?id=1020012

-- e10s-addons related chunk landed - https://bugzilla.mozilla.org/show_bug.cgi?id=990729 ; https://bugzilla.mozilla.org/show_bug.cgi?id=1017302 ; https://bugzilla.mozilla.org/show_bug.cgi?id=1019181

-- Cache2 related fixes - https://bugzilla.mozilla.org/show_bug.cgi?id=956801 ; https://bugzilla.mozilla.org/show_bug.cgi?id=967310

-- Cache2 porting to thunderbird - https://bugzilla.mozilla.org/show_bug.cgi?id=1023413