121–130 of 265 posts
I'm glad that they have released support for the Web Authentication API. Hopefully I won't need to use Chrome for websites I choose to be more secure with. Although, with a quick look it seems like I still can't use U2F with Google on Firefox.
Pocket Sponsored Stories will appear for a percentage of users in the US. Read about our privacy-conscious approach to sponsored content If you can't roll out a feature without violating EU privacy laws, you're not employing a "privacy-conscious approach."
Yeah, that's why I set the "extensions.pocket.enabled" to "false" in my about:config. It's such a weird feature in an otherwise pleasant browser.
Can someone explain this one to me? Does this mean I can't use "gi", "i", "image", and "is" as my Google Image Search keywords and need to pick one? Reading the issue [0] isn't helping me. I only recently updated to FF59 from FF39, having to abandon most of my workflow. I really hope this update isn't another nail on the stairs for me, seems every single update since FF40 has broken a significant piece of my workflow. I'd appreciate knowing before updating and then having to roll-back.
I haven't tried Firefox since version 47 and haven't used it as my main since 37. I gave 61 (dev edition) a spin yesterday. All the extensions that make the browser usable for me were like 1990s geocities pages: "Under Construction" if they existed at all. They were just placeholders that lacked most features with links to bugzilla pages to vote for features to be added back into Firefox. Garbage collection was prett…
1000 tabs? Why? How?
Unfortunately, looks like the CPU spikes are still a problem on OS X for me. I check this every time a new version is released as I'd love to make the switch from Chrome, but Firefox with one blank tab and no extensions uses more CPU than Chrome with 15 actual tabs. When I actually throw activity at Firefox it hogs the CPU even more. Here's hoping v61 addresses it.
Chiming in here. I would absolutely love to switch to Firefox for a host of reasons, ranging from "I don't want to use Google products" to "I love the tabs". Unfortunately, it's completely unusable for my workflow on a 2015 Macbook Pro with 16G RAM. I keep a variety of tabs pinned (JIRA, Zeplin, Gitlab, Jenkins, Invision, etc) and it seems as if they continue to hog a disproportionate amount of resources even when in…
At work, I have several GUIs in browsers that I access through Chrome, and they cause instant 3+ GB of usage. I can't test FF due to group policy, but anyway, Chrome can be a hog, too.
Are you saying that those same half dozen apps, when pinned in Chrome, do not cause any RAM issues for you?
But did they fix the weird scrolling friction on Android? Seriously, it's the main reason I don't use Firefox.
Despite this, I stick with Firefox because I want to use it - I can imagine that the vast, vast majority of users who have no opinion on which browser they use simply don't/won't put up with this and just go back to the easier to use Chrome. It's little things like this that make all the difference.
Unfortunately, looks like the CPU spikes are still a problem on OS X for me. I check this every time a new version is released as I'd love to make the switch from Chrome, but Firefox with one blank tab and no extensions uses more CPU than Chrome with 15 actual tabs. When I actually throw activity at Firefox it hogs the CPU even more. Here's hoping v61 addresses it.
I'm unsure if this is actually Firefox fault. I'm running Linux (arch and Ubuntu), Windows and macOS, and Firefox is only slow on macOS, while my macOS machine is the second most powerful machine I have. Running Firefox in a Ubuntu VM on macOS is faster than running it natively on macOS.
Unfortunately, looks like the CPU spikes are still a problem on OS X for me. I check this every time a new version is released as I'd love to make the switch from Chrome, but Firefox with one blank tab and no extensions uses more CPU than Chrome with 15 actual tabs. When I actually throw activity at Firefox it hogs the CPU even more. Here's hoping v61 addresses it.
I'm psyched to see the fix to https://bugzilla.mozilla.org/show_bug.cgi?id=1193394 released, which (amongst other things) mean that you can finally write code using both IndexedDB and promises without inadvertently committing the active transaction on promise resolution. Now I just need to wait until the market share of other Firefox versions decreases before I can actually take advantage in production :)
According to the CSV data available from http://gs.statcounter.com/browser-version-market-share new Firefox versions tend to dominate just 1-2 months after release. https://imgur.com/a/xzvAU4t