171–180 of 836 posts
Anyone know how the new FireFox compares on battery-life? Safari crushes Chrome on this front currently, but I'm curious how FireFox compares now.
None of the Firefox Quantum work has looked at power usage, so don't expect any changes on that front.
"AMD VP9 hardware video decoder support for improved video playback with lower power consumption"
Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
Unfortunately, I don't think theres ever going to be a Classic Theme Restorer equivalent that works going forward. https://bugzilla.mozilla.org/show_bug.cgi?id=1328244
Earlier quoted context omitted.
Can't seem to find where it is in firefox preferences. Could you please extend your solution?
This got me too. It's not in preferences, you have to use the hamburger menu thingy. Then, it's shoved randomly at the bottom. The overall design is really a mess in 57, although browsing does seem faster.
Earlier quoted context omitted.
The one extension I'm missing (which has been broken since e10s) is cliget: https://github.com/zaidka/cliget
FYI: Firefox (and other browsers as well I think) already have built-in functionality for generating a cURL command with all the headers and cookies included. In the dev tools, you can right-click on a request in the "network" tab and click Copy > Copy as cURL. Sadly, this only works for requests you haven't already done with the dev tools open and it doesn't generate wget commands, but you might get some use out of…
Earlier quoted context omitted.
If required APIs don't exist any more, how is that extension author's fault? (Tab Groups user here)
If they don't exist, sure, but most of the bickering is "I want XUL and nothing else". And how many of those lamenting the absence of some API have actually told Mozilla what they need? By all accounts Mozilla has been very responsive and helpful. Not everything was possible, but the problem lies mostly not on their side.
I don't know that that's fair. The discussions I've seen and participated in have revolved around equivalency, not identity.
> how many of those lamenting the absence of some API have actually told Mozilla what they need?
The Vimperator devs and some users have been very clear on that point.
> Mozilla has been very responsive and helpful. Not everything was possible, but the problem lies mostly not on their side.
Mozilla has indeed been responsive and as helpful as they can be given the constraints under which they operate. But extension developers aren't really to blame here either, because if WebEx doesn't include an API you can use to do what you need to do, then what option do you have? There's frustration on all sides - Mozilla devs, extension devs, and users. But we're all pulling together toward the same ultimate goal. I don't know what improvement anyone expects to elicit by trying to assign blame.
Earlier quoted context omitted.
You can change the theme to "light" in preferences. If should get rid of the black bar. This has been a common complaint from osx users.
Can't seem to find where it is in firefox preferences. Could you please extend your solution?
That particular welcome screen seems like a really poor choice to demonstrate the supposedly much-improved rendering engine on my machine.
Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…
https://chrome.google.com/webstore/detail/tabs-outliner/eggk...
I was a Firefox zealot before they decided to go in this direction. For me Chrome does all the things FF does but much faster(at the moment).
Earlier quoted context omitted.
Looks like a lot of wont be ported, limited functionality and lack of necessary APIs on that list. Doesn't quite give me much confidence in WebExtensions.
Note that the webextension APIs are still under active development. So just because the APIs don't exist yet doesn't mean that they won't ever.
In which case, switching to webextension support exclusively is premature at this point, don't you think? It would have been better to wait until the API was robust enough to allow 99.99% of legacy extensions to be ported.