Firefox 23 released

Firefox 23 is available through the internal updater and from the usual suspects such as Majorgeeks. My v22 updated quickly with no hiccups on extensions.

 

I updated through the FileHippo update service.

As forecast, FF came out on schedule today!

 

Thanks for the Info. I plan to update this evening.

 

Changelog, take note of the bold text...

It also has partial TLS 1.1 support, more info here:
https://www.wilderssecurity.com/showthread.php?t=351340

 

Yes, it seems like a good idea to change the default to "2" so FF will attempt to use TLS 1.1

 

wow they have removed that option from the GUI and from about:config

you now need an extension if you want a choice in the matter....

 

Tab Mix Plus is a good option for granular control over windows and tabs.

 

They really should stop removing options..



Vulnerabilities fixed:

https://www.mozilla.org/security/known-vulnerabilities/firefox.html

 

Would it be more accurate to say they're masking options? As long as there's a way to manually configure the settings it isn't an issue for me. After all Firefox is still far more configurable than anything else out there IME.

 

What would be the reasoning behind masking options?

 

That I don't know - I'm not suggesting it's a good idea.

 

Yes, they're mostly masking, in post 7# treehouse786 says it's also removed from about:config.

 

From ronjor's link:

And from here. https://blog.mozilla.org/security/2013/05/16/mixed-content-blocking-in-firefox-aurora/

Why aren't they giving us the option to block mixed passive content? This means I still need to look manually for the non-https content and block it myself. I will not enter financial information on a non-secure page.

I'm also getting tired of seeing options removed. So they remove options and expect me to use add-ons that slow things down and break compatibility? I guess it's time to move on from Firefox.

 

yeah and no reason given for the removal.

When I queried about the keepalive options been removed a while back I got something back "its good for the internet" so the change was sort of political by a developer who doesnt like people not using keepalive to access sites.

Most of the time tho developers dont even bother replying when asking about removed options, they have a like it or lump it attitude.

The removal of options is either because they want to force people to changes the developers want whether its gui or other changes and/or to make the code easier to maintain.

I expect in future the ability eg. to keep the menu always visible in firefox will eventually be removed. Firefox long term aim is to be a chrome clone.

 

Toggle security.mixed_content.block_display_content in about:config.

 

drives me crazy, believe didn't happen before v22, still persists in 23, in my case at least

is going to:

the only solution?

 

Thanks for the tip!

 

Thanks for the Info.

 

Does there need to be more than one solution?

 

This trend of Mozilla removing options and their apparent new desire to reset to default the changes I have already made is what is pushing me to find a new browser as well. I hate to do it as I am a long time FF user but it is looking to be inevitable. I am running an older version until I decide what to do. I could drop back to the latest ESR version of FF (and delay the inevitable) or go to another browser that supports NoScript, which I would like to keep.

 

Why not just disable automatic update so you can vet new versions of FF before install and adjust settings as necessary?

 

With the amount of vulnerabilities fixed this version I wouldn't consider holding to an old version a viable option. Especially with recent exploit that only affected the ESR.

 

If you read my post completely you should surmise that I have automatic updates disabled, as I stated I run an older version now.

How do I adjust settings as necessary when Mozilla is removing the settings?