updates Meet the browser: Firefox Next

[BooBerry]

Unicode 8.0 adds a total of 7,716 characters, encompassing six new scripts and many new symbols, as well as character additions to several existing scripts. Notable character additions include the following:

• A set of lowercase Cherokee syllables, forming case pairs with the existing Cherokee characters
• A large collection of CJK unified ideographs
• Emoji symbols and symbol modifiers for implementing skin tone diversity; see Unicode Emoji.
• Georgian lari currency symbol
• Letters to support the Ik language in Uganda, Kulango in the C

[gohpep]

http://techcrunch.com/2015/06/17/google-microsoft-mozilla-and-others-team-up-to-launch-webassembly-a-new-binary-format-for-the-web/

[The_Decryptor Veteran]

ugh, at least they're all working together on it.

Still, it lets developers skip a step or two, so I suppose it's a good thing.

[BooBerry]

ECMAScript 6, the Latest Version of JavaScript, Finally Released

Looking forward in FF41.

[The_Decryptor Veteran]

The latest OS X nightly has a pretty bad memory leak (an actual one) due to the switch from "POSIX" style shared memory to OS X style, I've had the browser open for an hour and it's at 14.4GB.

Edit: It's been fixed and the nightly has been re-built.

[tompkin]

http://www.computerworld.com/article/2936593/web-browsers/mozilla-restarts-work-on-multi-process-firefox.html

[The_Decryptor Veteran]

"restarts"

I didn't realize they stopped, considering they have been working on it for months.

[BooBerry]

Pale Moon to switch from Gecko to Goanna rendering engine

[bawz]

 

Pale Moon to switch from Gecko to Goanna rendering engine

 

this will be interesting, will people stay with PM or move back to Firefoxx itself.

[The_Decryptor Veteran]

Ha, got to love browser forks, especially when they're done for silly reasons (The version number being right up there).

I wonder if they're actually going to remove "Gecko" from the UA string, and how quickly they'll realize that's a bad idea. They might dislike the frozen build ID in the UA string, but it's there for a reason.

[Boo Berry]

I wonder if they're actually going to remove "Gecko" from the UA string, and how quickly they'll realize that's a bad idea. They might dislike the frozen build ID in the UA string, but it's there for a reason.

This. People will jump back to Firefox when websites don't work correctly. Not to mention extensions potentially being broken from this change. Fortunately, I gave up on Pale Moon some time ago.

[Pikey]

Hello folks!

 

I've been running the latest Nightly for some time now (or at least I thought I was ..?) but I've just noticed that the build no. in the 'about Nightly' dialog seems to be stuck at ....41.0a1 (2015-05-29)

 

Is that corrupted in some way do you think? , just curious really, I can try rebuilding the profile with Mozbackup I suppose if I need to.

[bawz]

Hello folks!

 

I've been running the latest Nightly for some time now (or at least I thought I was ..?) but I've just noticed that the build no. in the 'about Nightly' dialog seems to be stuck at ....41.0a1 (2015-05-29)

 

Is that corrupted in some way do you think? , just curious really, I can try rebuilding the profile with Mozbackup I suppose if I need to.

IMO you dont really need MozBackUp extension anymore  just backup your Bookmarks by going to

 

Show All Bookmarks > import & Backup > Export Bookmarks to HTML

 

an make a list of what Extensions you have

 

but what you could do is

 

make a New Profile an import your Bookmarks over to that Profile an check for an update of Nightly

[torrentthief]

mozbackup can back up loads of things, saved password, history, search terms in the address bar etc. The problem it has is that it won't work with 64bit firefox. I really hope the creator makes a new version that works with 64bit firefox.

[Pikey]

Thanks Demz ... that worked out nicely! ...

 

Of course as torrentthief points out though, I'm now missing some other stuff ... such as passwords!

 

I have successfully used Mozbackup before now to selectively 'rebuild' a profile so maybe I'll have a play around with that and see how we go!

[oldtimefighter]

http://www.computerworld.com/article/2936593/web-browsers/mozilla-restarts-work-on-multi-process-firefox.html

From the article...

 

"But even as Mozilla beefed up the engineering staff working on e10s, it also appeared to be rethinking its pledge to issue a 64-bit version of Firefox for Windows.

In the company's internal documentation for a 64-bit Firefox, Mozilla now hints that the initiative might be canned. "Before we continue to invest in the plan, we need to identify the market reward to either acquire or retain users vs. the cost of getting to GA" General Audience," the document stated."

 

WTF?

 

They already have a 64-bit beta release I have been using for months at work. It works for the most part and in some ways better then the stable 32-bit release...  Why is it so damn hard to have a 64-bit version of Firefox for Windows?

[gohpep]

From the article...

 

"But even as Mozilla beefed up the engineering staff working on e10s, it also appeared to be rethinking its pledge to issue a 64-bit version of Firefox for Windows.

In the company's internal documentation for a 64-bit Firefox, Mozilla now hints that the initiative might be canned. "Before we continue to invest in the plan, we need to identify the market reward to either acquire or retain users vs. the cost of getting to GA" General Audience," the document stated."

 

WTF?

 

They already have a 64-bit beta release I have been using for months at work. It works for the most part and in some ways better then the stable 32-bit release...  Why is it so damn hard to have a 64-bit version of Firefox for Windows?

Some plugins.

[oldtimefighter]

Some plugins.

Plugins should not cause them to cancel an offical 64-bit release. What's next? Holding off on a security update because it beaks a plugin?

[+Zlip792 MVC]

New door hanger UI for HTTP & HTTPS..

 

[The_Decryptor Veteran]

While I like the idea of flagging plain http:// as insecure, I foresee problems if they make it look like an error.

[gohpep]

While I like the idea of flagging plain http:// as insecure, I foresee problems if they make it look like an error.

Well, http should be considered like an untrusted certificate in my opinion. They both allow or hint at an attacker modifying a HTTP request or response.

[The_Decryptor Veteran]

Yeah, problem is the vast majority of sites are still plain HTTP, if you start flagging security warnings on them, you're going to train users to ignore the warnings more than you will encourage site devs to run over HTTPS.

Things like HTTP 2 and locking new web APIs to HTTPS origins only are what will encourage devs to move, not "showing" a warning to their users.

[MikeM97]

Yeah, problem is the vast majority of sites are still plain HTTP, if you start flagging security warnings on them, you're going to train users to ignore the warnings more than you will encourage site devs to run over HTTPS.

 

Exactly.

I've tried this too...

[gohpep]

Yeah, problem is the vast majority of sites are still plain HTTP, if you start flagging security warnings on them, you're going to train users to ignore the warnings more than you will encourage site devs to run over HTTPS.

Things like HTTP 2 and locking new web APIs to HTTPS origins only are what will encourage devs to move, not "showing" a warning to their users.

Yeah, just like Windows UAC. However, I think that HTTP support should eventually be disabled by default in browsers, just like how SSL is disabled by default.

 

However, there will be a lot of trouble for many websites for them to move to HTTPS.

[BooBerry]

Rust 1.1 was released today as stable while Rust 1.2 has entered beta.