porno

Mozilla Firefox 40 Released



/ 1 year ago

firefox 1

Firefox’s existence has been somewhat rocky over the past few years, from the browser market becoming more competitive with the increased competition from Google Chrome to Microsoft’s new Edge browser, to the irritated reaction from Mozilla’s CEO who has rallied against Windows 10 over how consumers select a default browser.

So what does the latest incarnation of Firefox have in store for consumers? Well, Firefox 40 is out today (11th August 2015) which sees mostly under the hood improvements. These include enhanced compatibility with Windows 10, although previous versions do work with the new OS, this is more moving the browser in line with touchscreen devices and includes “close” buttons on tabs which are now bigger and the address bar also has bigger fonts. It has also revised tabstrips and toolbars plus a custom Windows 10 theme.

Other key changes include an improved and expanded malware detection feature in Firefox, which is able to identify malware downloads in all supported platforms as well as warn users about potentially unwanted software. Users can also receive suggested titles in the new tab page based on categories Firefox matches to browsing history. Improved scrolling, graphics, and video playback performance with off main thread compositing (GNU/Linux only) and a Graphic blocklist mechanism improved: Firefox version ranges can also be specified, limiting the number of devices blocked, and smoother animation and scrolling with hardware vsync (Windows only)

Warnings for unsigned extensions will be displayed and they’ll be blocked completely in Firefox 41

As for security, the below image illustrates what has been fixed in Firefox 40,

firefox

This update will be rolled out within the next day or so within the standard methods, Firefox might also need to revise the new version naming, otherwise it won’t be long before we reach Firefox 100 and above.

Thank You Firefox Notes for providing us with this information

Image courtesy of Fanpop


Topics: , , , , , , , , , , ,

  • Peter Ck

    I’m so glad all those things like “Redefinition of non-configurable JavaScript object properties” have been fixed. I’m always complaining about redefinition of non-configurable JavaScript object properties. Only the other day I thought: if I experience one more redefinition of non-configurable JavaScript object properties, I’ll probably suffer a massive heap overflow in gdk-pixbuf :-/

  • Peter Ck

    I’m so glad all those things like “Redefinition of non-configurable JavaScript object properties” have been fixed. I’m always complaining about redefinition of non-configurable JavaScript object properties. Only the other day I thought: if I experience one more redefinition of non-configurable JavaScript object properties, I’ll probably suffer a massive heap overflow in gdk-pixbuf :-/

  • Peter Ck

    I’m so glad all those things like “Redefinition of non-configurable JavaScript object properties” have been fixed. I’m always complaining about redefinition of non-configurable JavaScript object properties. Only the other day I thought: if I experience one more redefinition of non-configurable JavaScript object properties, I’ll probably suffer a massive heap overflow in gdk-pixbuf :-/

  • Peter Ck

    I’m so glad all those things like “Redefinition of non-configurable JavaScript object properties” have been fixed. I’m always complaining about redefinition of non-configurable JavaScript object properties. Only the other day I thought: if I experience one more redefinition of non-configurable JavaScript object properties, I’ll probably suffer a massive heap overflow in gdk-pixbuf :-/