Mozilla Firefox Browser Stable Version Releases

Yes, it's not new but the improved UI is - which was what I was reporting, nothing else.

I think the Updates Team member was insinuating that I was trying to reinvent the wheel

 

Ok. But, i am still unable to figure out what was improved.. Sorry, it seems to be looking exact way to prior version to me...

 

The right-click menu dialogue has improved of which I'm unable to provide a screen capture.

 

B/w I am intereseted to see if OMTC and Cache v2 brings any improvements in responsiveness area

 

Please post back a link to the add-on that allows this. Disconnect have confirmed that the URL https://search.disconnect.me/ cannot be used as a search engine in Firefox although I have no specifics other than what they (Disconnect) informed me on Twitter.

Again - this is the Mozilla KB article.
https://support.mozilla.org/en-US/kb/search-bar-add-change-manage-search-engines-firefox

You may use Disconnect as search with Firefox but not set as a (search engine) - specifically.

 

https://addons.mozilla.org/en-US/firefox/addon/add-to-search-bar/ (to add the search engine)
https://addons.mozilla.org/en-US/firefox/addon/omnibar/ (to change search engines from address bar)

 

It helps to read release notes

• New - Easier back, forward, reload, and bookmarking through the context menu

 

hmm...I know the right click UI was changed.
I was quoting on Re. Permission tab of the Page Info window. I was confused initially with the screenshot he attached.
Later he had clarified in his post #53.

Anyway, thanks for your effort in putting the screenshot. I think you used some 3rd part screen capture tool!!

 

There's also the visual method which works somewhat like Internet Explorer.

For most that use MSIE | IE or Internet Explorer which are all the same Browser, reading and participating at Wilders is a learning experience. It should not be assumed we're all experts 100 % of the time.

 

I use Disconnect Search as a search engine using this extension.

 

@JRViejo: The camera and microphone permissions are related to getUserMedia (javascript access to camera/mic) and WebRTC (web real-time communications, including video/voice streaming and chat). Those are two terms that will get you some hits.

 

My pleasure

Here's some info from the Perspectives Blog page:

http://perspectives-project.org/2014/05/14/perspectives-4-5-1-released-polski/#comments

"thanks for the note. Yes, we are aware of this and actively working to fix it. There is a bug in the bug tracker here –"

https://github.com/danwent/Perspectives/issues/123

 

Hi J R. To check what you like to know, I reinstalled (sandboxed) Firefox 30 and Firefox 21. In Firefox 30, the about permissions page looks exactly the same as in Firefox 32. In Firefox 21, the Camera & Microphone permissions were not incorporated yet. I ll find out later for you when I have a little bit of time exactly the version in which they were first incorporated for the first time. But it whats done in one of the versions between 21 and 30.

Bo

 

Thanks, and good to read that they're moving away from MD5.
EDIT:I also noticed that when viewing certificates in Firefox it now shows SHA1 and SHA256.

 

J R, it was in Firefox 30. Firefox 29 did not show anything regarding Camera & Microphone permissions in about permissions.

Bo

 

Anyone using Video DownloadHelper might be interested, beta 4.9.24b1 fixes issues in many sites (not YouTube) caused by changes in Firefox 32 cache API. It works for me.
http://www.downloadhelper.net/install-beta.php?version=4.9.24b1

Bo

 

While browsing the release notes I spotted this:

Make gUM permissions (audio-capture, video-capture) allow by default for certified apps
https://bugzilla.mozilla.org/show_bug.cgi?id=1021643

What it seems to be describing is allowing "certified apps" to bypass camera/audio/video permissions configured by the user. I think Firefox OS apps, particularly the Loop client which uses WebRTC, are the focus. However, Firefox desktop supports some kind of apps too and it is meant to support Loop. So maybe it or at least the mentality will apply to desktop too. I don't know. Seems noteworthy, thus this note.

FWIW, I also spotted:

Rename Seer to Predictor
https://bugzilla.mozilla.org/show_bug.cgi?id=1016622

Predictor as in predictive networking connections and requests. Those who want to disable that type of thing might want to update their preference changes, notes, whatever (network.seer.enabled -> network.predictor.enabled for example). It looks like it is still off pending the rewrite: https://bugzilla.mozilla.org/show_bug.cgi?id=1009122

Edit: Forgot another item of interest...

Decide how to expose the option to disable openh264
https://bugzilla.mozilla.org/show_bug.cgi?id=1007694

 

Loop (audio/video chat) has moved to Beta 33.
The Cisco plugin, the (telephone receiver) icon and functional widget.

 

I wouldn't run BETA software or add-ons on my FINAL release Browser unless there was a compelling reason and I fail to see one.