- Added Guarani (gn) locale :) Thank you
Tereiko porãke! Rojhayhû. ;)
Firefox 50.0
101–110 of 205 posts
Re: Firefox 50.0
#102"CVE-2016-5292: URL parsing causes crash" made me curious, given the talk I've heard about rust-url being integrated into Firefox.
For anyone else interested, it appears that the patch is still being reviewed - https://bugzilla.mozilla.org/show_bug.cgi?id=1151899 (though I don't know if rust-url would have actually prevented the issue).
Re: Firefox 50.0
#103>Added download protection for a large number of executable file types on Windows, Mac and Linux It seems archives (such as .bz2, .gz) are treated as executable files. What is the reason for that? https://hg.mozilla.org/mozilla-central/file/054d4856cea6/too...
My best guess would be that there is still some risk with these archive types since the browser-client has built in automatic decompression for them.
Re: Firefox 50.0
#104If they could just add a decent profile management option, I would switch back from Chrome. Keeping my work and personal accounts separated is the only thing keeping me using that battery killer
If you're willing to try Firefox Nightly, check out the containers experiment: https://wiki.mozilla.org/Security/Contextual_Identity_Projec... While everything still happens within a single profile, sites in different containers get different storage (cookies, localStorage, IndexedDB, etc.) and cannot see each other.
Cool.
I've been using a combination of NoScript,Self-destruction coockies,ublock and a personal vimperator script to wipe out all that nasty stuff when I close the window.
https://github.com/liloman/dotfiles/blob/master/vimperator/....
https://github.com/liloman/dotfiles/blob/master/Scripts/Scri...
By the way firefox is pretty nasty by default and you must do a lot of hard work to evade tracking, in special by google:
https://github.com/liloman/dotfiles/blob/master/vimperator/....
Of course you must use custom fonts if you don't want to be tracked by google for every single webpage you enter.
I think I will play with containers for firefox when I try firefox 50. Something like a new container for every tab, I reckon It must be pretty easy with vimperator(or whatever plugin you like) to make .
Put your vimperator/penta/vimium/X to work for you. :)
Re: Firefox 50.0
#105Earlier quoted context omitted.
In the past the GTK3 code path was tested only by Red Hat as the primary developer of all things GTK and GNOME. At that time, there was only a GTK2 build from Mozilla, and now instead of doing the same as Windows 32-bit/64-bit we're presented with just GTK3 support with the promise to obsolete the GTK2 code, while seemingly not considering the regressions of GTK3. Why do we use Mozilla binaries of Firefox on linux di…
The "EME-free" build differs only by the default value for the "Play DRM content" checkbox. You can put a normal build in the equivalent state by unchecking the checkbox.
Good to know. I thought it doesn't include and prevent the download of some DRM blobs.
Re: Firefox 50.0
#106Earlier quoted context omitted.
I don't know about Firefox or Atom, but in Chromium you can achieve that via Ctrl-PgUp and Ctrl-PgDn.
Which is a pretty dumb shortcut to use one handed and compared to alt+tab.
I have never seen a keyboard which doesn't have a Ctrl on the right side.
Re: Firefox 50.0
#107Earlier quoted context omitted.
I don't know about Firefox or Atom, but in Chromium you can achieve that via Ctrl-PgUp and Ctrl-PgDn.
Which is a pretty dumb shortcut to use one handed and compared to alt+tab.
It exists for ages already, though. You use the same shortcuts to cycle tabs in dialog boxes. And that goes back to at least Windows 95, if not further.
Re: Firefox 50.0
#108Earlier quoted context omitted.
In the past the GTK3 code path was tested only by Red Hat as the primary developer of all things GTK and GNOME. At that time, there was only a GTK2 build from Mozilla, and now instead of doing the same as Windows 32-bit/64-bit we're presented with just GTK3 support with the promise to obsolete the GTK2 code, while seemingly not considering the regressions of GTK3. Why do we use Mozilla binaries of Firefox on linux di…
> While it is easy to build with cairo-gtk2 as the backend, that code path, as I wrote in a sibling comment, reliably crashes for me anytime I try to do File-Open. That points towards GTK2 support possibly not being functional, which could be a good reason why they don't provide a build for it, even if they wanted to. It sounds like the real problem here is that Mozilla is changing stuff that some people don't want c…
Good points. Just finished building firefox 50.0 with for cairo-gtk2 and trying it out now. Hope there are no crashes.
I agree with what you say and want to add that there two issues here. First is the GTK3 port of Firefox not working as a native Wayland GTK3 window. Second is the themeing issues with GTK3 that people ran into, which is something you can live with. Finally, it's the serious regressions of GTK3 itself which go unnoticed or ignored as evident in the gnome.org bug-tracker and the tickets I've linked to in a sibling comment.
The most important argument for Mozilla providing GTK2 builds is that otherwise the likelihood of the code bitrotting is very high as it happened with the Qt port. The interesting aspect of the Qt port was that at that point in time GTK2 was the best choice, but now for substantiated reasons major applications chose to rather port to Qt than GTK3. Therefore, if the Qt port were to be revived it's much more likely to be of interest and maintained than back when the GTK2 port was good enough that nobody cared about Qt.
I know X11 and Wayland are not Mozilla's main platforms of interest and I'm grateful that they do support with the feature set they do. I'm surprised at the seemingly isolated echo chamber perspective of the GTK3 devs. It's an interesting behavior to observe since without non-GNOME users it could just as well be rolled into GNOME itself. Interesting times, having lived through the times when jwz in 1998 was debating whether GTK1 was any good for Linux.
Re: Firefox 50.0
#109Earlier quoted context omitted.
GTK3 itself has various regressions and is slower than GTK2 despite the architectural refactoring lending itself to a snappier experience. https://bugzilla.gnome.org/show_bug.cgi?id=771708 Firefox GTK3 has regressions too, for instance the bookmark manager not remembering where you were last which works with Firefox ESR (GTK2). https://bugzilla.mozilla.org/show_bug.cgi?id=1267863 Also GTK3's file dialog is subjective…
Serious comment:why bother with gtk anyhow and move to Qt?
I love GTK2, but I can do without GTK3, seeing we're at 3.22 and it's still not as stable or regression free as GTK2.
I'd be the first to build and use a Firefox where the Qt port was updated and made to work but GTK is the GUI toolkit used by Firefox outside Android, macOS and Windows. That said, GTK2 was and still is very good at what it does. It just works but doesn't support Wayland.
I cannot move to Wayland anyway until xterm or rxvt-unicode are ported since XWayland integration is still imperfect. Like they wrote in the bug report, while GTK2 doesn't have a Wayland backend, GTK3's backend isn't really production quality either with dialogs sometimes opting to zoom out rather than scale out or general stability issues. If you try to start Firefox under Wayland by telling GDK to use Wayland, it just crashes on startup.
Re: Firefox 50.0
#110Earlier quoted context omitted.
I have this feature in sublime text & Atom and absolutely hate it. I feel like ctrl + tab has to move to next tab & ctrl + shift + tab should move to previous tab (cycle if it reaches the end). I feel like that's more predictable behaviour.
Can be fixed in Sublime Text as follows: { "keys": ["ctrl+tab"], "command": "next_view" }, { "keys": ["ctrl+shift+tab"], "command": "prev_view" }
Ctrl+shift+P then type "key bindings user"