3 ms·
These are some good changes. Perceived performance is very important for a program you use many times per day. One of my long time complaints is that with Chrom
by ajnin 5y ago
These are some good changes. Perceived performance is very important for a program you use many times per day. One of my long time complaints is that with Chrome, when I want to search for something I'll often ctrl-N to open a new window and then type my query. Even if it takes a little bit of time to show the window my query will be right there in the search bar. With Firefox, those keystrokes are lost. I hope this fixes that.
- nyanpasu64 5y agoFor as long as I can remember, Firefox has always been janky and slower than Chrome at moving tabs in and out of windows. Dragging a tab doesn't always create a new window, sometimes it acts as bookmarking if I drag it into the tab bar, sometimes (on Linux) it acts as drag-dropping the tab into another app like Discord and fails to open a window. Dragging a tab out of a window doesn't create a new window until you release the mouse, so it feels unresponsive, and you don't know whether you'll get a bookmark or tab or nothing at all. And dragging the last tab out of an empty window doesn't close the window to allow me to see what windows lie underneath. And in the past (not sure now) I've noticed that dragging a tab a few pixels downwards would create a new window, when I meant to click or reorder a tab.
- arp242 5y ago> And in the past (not sure now) I've noticed that dragging a tab a few pixels downwards would create a new window, when I meant to click or reorder a tab. I've had this problem for a long time as well; it's very hard to reliably reproduce too. I ended up finding some about:config setting to just disable this entire feature, and my life has been better since.