Earlier quoted context omitted.
Possibly for the same reason they don't ship Tk compiled versions. Why should they target every GUI toolkit and complicate their build process which they then have to deal with supporting? If it's that easy, you can probably find some third party that compiles and offers it. I'm not sure why you think Firefox needs to do it themselves.
For the same reason they haven't made 64-bit the default on Windows and provide two versions. There are many users for whom only one variant works reliably. If upstream, like in the case of cairo-gtk3, decides GTK2 is not supported anymore, it's a matter of chance whether your cairo-gtk2 build of Firefox works at all. For instance, for me 49.0.2 gtk2 local build on Arch crashes anytime I try to use the file dialog, w…
Firefox 50.0
71–80 of 205 posts
Re: Firefox 50.0
#72Earlier 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.
Is there a way to disable this ctrl+tab behavior in Sublime Test? I can't stand it either.
On Atom, I've set ctrl + tab to remap to pane:show-next-item, and ctrl + shift + tab to pane:show-previous-item.
(view your keymap, and see what ctrl + page-up/down is bound to, and then bind it to ctrl + tab /+ shift)
Edit: here are my settings:
'body':
'ctrl-tab': 'pane:show-next-item'
'ctrl-tab ^ctrl': 'unset!'
'ctrl-shift-tab': 'pane:show-previous-item'
'ctrl-shift-tab ^ctrl': 'unset!'Re: Firefox 50.0
#73"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)
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.
If you only have a few tabs open, it can be useful in conjunction with Ctrl-[1-9], but I am also still strongly in the next/prev tab camp.
Re: Firefox 50.0
#74"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)
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.
I don't use ST, but at least in Atom, I know you can easily override it in your keymap:
'body':
'ctrl-tab': 'pane:show-next-item'
'ctrl-tab ^ctrl': 'unset!'
'ctrl-shift-tab': 'pane:show-previous-item'
'ctrl-shift-tab ^ctrl': 'unset!'Re: Firefox 50.0
#75Did something change in font rendering with Freetype on Linux? While 49.0.2 with FreeType 2.7 looked the best (subjectively) I've seen any font rendering (including Windows 10 and OS X Snow Leopard (been a while)), something off with 50.0's rendering. I haven't enabled any custom render options, just your typical archlinux freetype 2.7 desktop. Time to get ESR and compare with that but would be great to hear back fro…
Freetype 2.7 introduced a new rendering engine. I cannot link anything at the moment but the Arch Forums have pretty detailed help.
Re: Firefox 50.0
#76Breaks NoScript on launch day. That was an unpleasant surprise this morning...
Re: Firefox 50.0
#77"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)
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.
And I love it :-p It is literally the reason (in combination with "open new tab next to current") I use the browser I do (Vivaldi; would consider Opera, but it doesn't/didn't do "open new tab next to current").
To each their own :-)
Re: Firefox 50.0
#78"Set a preference to have Ctrl+Tab cycle through tabs in recently used order " Finally something that is an actually improved UI feature! Not some "removed status bar and instead hover its info over text you want to read sometimes" or "moved refresh button to different place than before just to annoy you" or similar thing :)
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.
{ "keys": ["ctrl+tab"], "command": "next_view" }, { "keys": ["ctrl+shift+tab"], "command": "prev_view" }
Re: Firefox 50.0
#79Earlier quoted context omitted.
I was confused by what this meant - so perhaps some others are too. This is what a few minutes of research got me: Uploading individual files in a directory = was possible Uploading an entire directory (eg: a folder to a cloud storage service) = was not possible Personally my workflow means I've uploaded the contents of a directory to a directory I make myself, so I've never encountered the problem. Am I missing some…
You can't upload subdirectories, so it quickly becomes painful to upload an entire directory of files if it has multiple folders within.
Thanks for the response!
Re: Firefox 50.0
#80Earlier 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.
It's all personal preference, but since Opera 12 I've been addicted to ctrl-tab for most recently used switching (Opera 12 had a nice tab switcher that made the interaction very understandable/manageable), and then alt-tab for switching in "physical" order. (I run a large number of tabs, and quickly switching between two (or a small number) that I've used recently seems to be a common interaction for me - but then be…