updates Meet the browser: Firefox Next

[The_Decryptor Veteran]

If you want to keep up with changes, yes.

[bawz]

There are things that must be fixed. Under-the-hood for example. Does that mean we should install Nightly? -.-

install Nightly but also use it to report Bugs. if not keep using stable release channel 

[Konstantine]

Thanks guys! :) If I find any, I will. :p

[+Neyht Subscriber²]

For anyone using Heartrippers metro for austrailis stylish script you can make this edit to the script to get rid of an unnecessary border around the menu footer.

#PanelUI-footer{
    border-top: 1px solid #e5e5e5 !important;
    padding: 0px !important;        /*------------was 6px-------------*/
    background: #f6f6f6 !important;
}

...or just remove the padding line completely.

 

[bawz]

The next beta will be 27.0b4 on 01/08/2014 -- so Beta3 will be skipped 

 

https://blog.mozilla.org/meeting-notes/archives/1622

 

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/27.0b4/

[bawz]

here's my Australis Discussion thread i made http://forums.mozillazine.org/viewtopic.php?f=23&t=2400725 an Ends at 65 

 

an here's JoeG's same Discussion http://forums.mozillazine.org/viewtopic.php?f=23&t=2760761&start=720 an end on 49

 

GO ME :D 

[ZeDestructor]

yes, Decryptor, shared memory o/& common-core process have been very way to reduce memory overhead. but such approach doesn't improve stability & security + it pounds the speed.

script blockage is better method to avoid viruses from untrusted resources, sandboxing ruins speed so badly much. in short, i vote for single-process scheme :)

 

You're confusing shared process and shared memory. Shared memory is having different processes have independent pages (memory addresses) that point to same blocks of actual physical memory. This is done at the OS kernel level and completely transparent and independent to programs. Modern kernels even implement cool stuff like copy-on-write so differing version can co-exist without needing to have multiple copies of identical data.

 

sandboxing traces code to prevent malware activities, so it needs a huge bulk of extra ticks on CPU & extra data moving as well. + needless to mention, JS code ain't very fast even w/o any sandboxes. + sandbox cannot guard against all kinds of malicious code & can crash process as well.

 

 

sandbox runs in the simplified form like:

 

1. recognize action.

1.1. if action is pure threat, prevent its execution.

1.2. if action is possible threat, inform user about.

1.3. if No threat detected, pass through.

======================================

ideally, considers that sandbox cannot be visible by testified code. but(!), in fact, no sandbox can emulate environment for 100%, so code could conceal its dark sides + in some cases, it's possible to crash sandboxing from testified code.

 

You are confusing heuristics (behavioural monitoring) and sandboxing. Sandboxing refers to letting the thing run wild in a closed, confined space (a sanbox if you will) and do all the damage without being able to access anything important and then just wiping it all off and starting back from scratch. A more extreme version of that is running like Deep Freeze on your computer and having the entire OS wiped every time you finish, or running a static virtual machine.

 

NB: some of this info may be slightly wrong, since I haven't done the OS design courses at my uni yet (doing them this year), but that is the general gist from reading quite a bit of documentation and talking about this stuff to friends who have done this stuff already.

[.stan]

For any windows8/firefox nightly user: http://userstyles.org/styles/96014/firefox-australis-windows-8-appearance

[Zmark]

For any windows8/firefox nightly user: http://userstyles.org/styles/96014/firefox-australis-windows-8-appearance

I'm using this. It's a good one.

[Kaoxt]

Anyone know why Firefox displays ESPN mobile different then Chrome or Safari on tablets or phone? Loving Australis updates on UX channel. Just wish certain sites wouldn't look different on Firefox.

[The_Decryptor Veteran]

ESPN does UA checking and doesn't send their normal mobile site to Firefox.

[Kaoxt]

Thanks! Wish there was a workaround. Glad to finally figure out the issue.

[The_Decryptor Veteran]

I think that even if you spoof the UA the site doesn't render properly, relies too much on non-standard WebKit stuff.

Same reason Google Images is broken in Firefox on a tablet too, it relies on a WebKit bug to work properly.

[ObiWanToby]

Firefox 29a1 nightly seems to not display HTML5 youtube video, gives me a flash warning everytime. The video is playing through, because I hear the audio of the actual video. I assume the overlay that says I need flash is covering the playing video.

[ObiWanToby]

I think that even if you spoof the UA the site doesn't render properly, relies too much on non-standard WebKit stuff.

Same reason Google Images is broken in Firefox on a tablet too, it relies on a WebKit bug to work properly.

 

We are 3 years away from Google requiring Chrome for all their advanced site features. They seem to ignore Firefox and IE in these cases, it is weird...

[bawz]

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/27.0b5/ out Now 

[The_Decryptor Veteran]

I eagerly await 27, because 26 has a bug with Android 4.4 where it will randomly crash, and it was fixed in 27.

Also TLS 1.1/1.2 and AES GCM.

[bawz]

I eagerly await 27, because 26 has a bug with Android 4.4 where it will randomly crash, and it was fixed in 27.

Also TLS 1.1/1.2 and AES GCM.

im really hanging out for 28 . i hope i will not need Adobe crap no more, , my love for Firefox might be re-ignited then 

[bawz]

this is good News for Fx users in Fedora an prolly other Distro's

 

http://www.phoronix.com/scan.php?page=news_item&px=MTU2OTk

 

 

GTK3 Version Of Firefox Up For Fedora Testing

 

https://lists.fedoraproject.org/pipermail/devel/2014-January/193827.html Martin Stransky a Mozilla Dev who also works for Redhat has built Fx from Source 

[The_Decryptor Veteran]

The Phoronix article is slightly wrong regarding Wayland support, Firefox talks directly to X11 for a few things, so moving to GTK3 won't allow it to run natively on Wayland.

[bawz]

The Phoronix article is slightly wrong regarding Wayland support, Firefox talks directly to X11 for a few things, so moving to GTK3 won't allow it to run natively on Wayland.

thats correct, i think Firefox still needs to be ported over to run on Wayland Natively . i dunno what the Progress of that is. something i'd possibly have to ask Martin 

[The_Decryptor Veteran]

I'd say it's blocked on GTK3 and all the OpenGL work (Currently it only uses OpenGL for WebGL, not the UI, that needs to be done ideally)

Edit: Also, plugins suck. What they'd want to use is similar to on OS X or Windows where you pass around handles to the hardware buffer and use that (Which is actually a lot like the underlying wayland protocol, which is funny).

Edit: Also, Bug 939709, as a side effect of moving from Cairo to Skia they can get rid of all the xrender junk (And then you have SkiaGL, so they could do all the drawing on the GPU, like what the Glamor DDX offers). It could be done with plain Cairo, but they want to move away from Cairo on all platforms so why do the work now when Skia would do it anyway.

[bawz]

http://worldofgnome.org/firefoxgtk3-fedora-repos-are-now-available/

[The_Decryptor Veteran]

It looks like Mozilla are planning on making official 64bit builds for Windows, there's some issues holding them back currently but I'd expect them to get fixed soon enough (Plugins are harder to fix, as usual)

[bawz]

with RHEL7  an onwards there no longer putting out 32bit  , instead its just 64bit an other Arch's . so yeah 64bit is the way to go however its gonna upset a lot of people that still only haver 32bit systems that cant afford 64bit Arch