Meet the browser: Firefox Next

By bogas04
in Web Browser Discussion & Support

 Share

Recommended Posts

Mentor

Neyht Member

Posted
  • Member
Posted

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.

 

Experienced

bawz

Posted
Posted

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 

Neowinian

ZeDestructor

Posted
Posted

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.

Grand Master

ObiWanToby

Posted
Posted

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.

Grand Master

ObiWanToby

Posted
Posted

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...

Experienced

bawz

Posted
Posted

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 

Experienced

bawz

Posted
Posted

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 

Experienced

bawz

Posted
Posted

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 

Grand Master

The_Decryptor Veteran

Posted
  • Veteran
Posted

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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing