381–390 of 836 posts
Just upgraded. Definitely feels snappier at first glance, what I'm most curious about however is how much the speed deteriorates the longer I use it (if at all). The older version was definitely pretty bad after a couple of days of uptime. All in all though. Nice job so far. :) Edit: I do sorta feel like the tabs are now smaller (when there is a lot of tabs open), any way to make them bigger?
Feedly performs like garbage with the new Firefox. 100% of CPU when clicking on the feed and doesn't go down.
Tab Groups (which was originally a first-class Mozilla feature called Panorama) absolutely changed my browser workflow, and I can't imagine regressing...
The new APIs won't support replacement any time soon, and the dev has already given up, since they'd already had to run a fundraiser once to add Electrolysis support, just to find that their work would be thrown away in the near future anyways.
And that's just one example... :(
Earlier quoted context omitted.
I'd say that the most sensible choice in the absence of any payment, considering FF sensibility and message, (i.e. according to me) DDG would be the most sensible default. (edit : clarify)
When has any proof ever been given that they’re any more privacy conscious than any other search engine?
There is a noticeable lag before first paint of the page. This is specially visible if you have a fast site. I was able to click through links on the site with no lag, now there is a small, but noticeable lag.
Also, where did the "Restore tabs" button go from the homepage?
EDIT: Also, it looks like my fans are running more often, so CPU usage could be higher as well.
For those who look for NoScript replacement, uMatrix[0] (from the maker of uBlock Origin) has got you covered (with "A Desperately Needed User’s Guide"[1]). [0] https://addons.mozilla.org/en-GB/firefox/addon/umatrix/ [1] http://adamantine.me/index.php/2015/11/18/umatrix-desperatel...
Tried this. It was too complicated and slow enabling every subdomain by hand.
I personally just stick to base domains usually. When a site is broken, allowing one or two 3rd-party base domains is often just enough to fix it.
If you want to go subdomain-granularity, this is your choice -- it's not forced on you. Some even go as far as subdomain/type (the cells in the middle).
I'm using it now. It is really snappy! There are bugs though. I'm using Debian Stretch. Right click menu doesn't work: it appears for a fraction of a second then disappears; so does the top-bar menu of LastPass plugin.
Is there a repo for FF57 for Stretch? If not, what is the "best" way to get it?
>Jessie and Stretch backports of Firefox release and beta are gone because of the requirement of rust to build them, which is not available in Jessie or Stretch. Please update your apt sources to use Firefox ESR instead.
I've downloaded the tarball from the firefox homepage, extracted it, and put it in ~/opt, and symlinked it to ~/bin/firefox, which is on my path first.
I write software for the web so speed is secondary. I want to know: Does the inspector have better/more features than Chrome's Inspector? Does it have Redux and React Toolbars that are better than the Chrome ones?