A little OT, but how can I enable/use the Screenshots feature? I cannot find it.
I think that's been around for a while, right? It's under my right-click menu.
I cannot see it there either.
Firefox 59 released
51–60 of 233 posts
Re: Firefox 59 released
#52Firefox is dead to me ever since they killed their addons and marketed it as a step forward. If I wanted to use Chrome I'd use fucking Chrome.
Re: Firefox 59 released
#53Congratulations! What's the memory usage like compare to earlier versions?
Looking at that bug, one problem with implementing the nonstandard "mousewheel" event is that the browsers that implement it have different behavior in terms of what the delta value means, so sites using it tend to do browser sniffing to decide how to handle it. Which means implementing it is likely to break sites unless you exactly match the UA string and behavior of some other browser.
Given that, and given that Firefox does support the per-standard "wheel" event, what is the argument for implementing "mousewheel"?
Re: Firefox 59 released
#54Sadly, still unusable for me since the Quantum update. A clean install and profile, no add-ons, and google.com/maps (for example) will max out my cpu. There must be some bug related to old hardware and OS (Macbook Pro 2009 + 10.11.x) or more people would be experiencing this.
Same for me on a 3.5 GHz Intel Core i7 13" Macbook pro. I had to revert back to Chrome.
e.g. Animations on stripe.com would auto max out my CPU.
Re: Firefox 59 released
#55Earlier quoted context omitted.
chat apps like discord and slack, mostly
Even discord and slack I don't want browser notifications. Inside their own tab, I can deal with ui elements. There's no need nor no want to have a page alert outside of the web page itself.
It can be useful when you get mentioned, like for example, a user has pinged the moderator role where a quick reaction will be necessary. Desktop notifications can significantly reduce reaction time to important events (though, assuming you do the sane and set Discord to only notify you on mentions that aren't @here or @everyone)
Re: Firefox 59 released
#56"Added settings in about:preferences to stop websites from asking to send notifications" Been waiting for this one.
Sites have been replacing the actual API request with a HTML5 overlay, precisely because of this - only when clicking "notify me" does the actual permission get requested, with the requisite dialog. (The rationale is "once the permission is denied, there's no way to bring it up again; a dismissed HTML5 box can be brought up again an infinite number of times") As for me, I went for WebAPI Manager, which blocks most of…
I usually disable JS and white list the sites that actually deserve it.
Re: Firefox 59 released
#57Switched to FF Nightly from Chrome about 6 months ago because Chrome's memory usage was awful. Firefox has been much better, especially since I modified the following in about:config: browser.sessionhistory.max_total_viewers => 0 dom.ipc.processCount => 1
Isn't limiting the ipc processes severely capping (CPU) performance?
It's a tradeoff, IMO.
Either you spare a few CPU cycles or a bit of memory. Though chrome doesn't seem to be doing good on either front.
Re: Firefox 59 released
#58Sadly, still unusable for me since the Quantum update. A clean install and profile, no add-ons, and google.com/maps (for example) will max out my cpu. There must be some bug related to old hardware and OS (Macbook Pro 2009 + 10.11.x) or more people would be experiencing this.
Same for the mobile version. It's unusable on single core devices.
Re: Firefox 59 released
#59Earlier quoted context omitted.
Sites have been replacing the actual API request with a HTML5 overlay, precisely because of this - only when clicking "notify me" does the actual permission get requested, with the requisite dialog. (The rationale is "once the permission is denied, there's no way to bring it up again; a dismissed HTML5 box can be brought up again an infinite number of times") As for me, I went for WebAPI Manager, which blocks most of…
Right. This is also the current standard approach for asking for iOS push permissions. Without intermediary dialog, the app can't try again.
And as app builders you have to explain people how to enable the permission anyways if people try to e.g. use their current location. Luckily since a few versions now, iOS allows apps to directly open a certain settings page, e.g. location services.