Εμφάνιση ερωτήσεων με ετικέτες: Εμφάνιση όλων των ερωτήσεων

All webpages continue scrolling after I've taken my fingers off the touchpad

I've just switched to Firefox as Chrome keeps lagging. I'm running Fedora 31 and the latest version of Firefox 76.0.1. When I use the 2 fingered scrolling and take my fin… (διαβάστε περισσότερα)

I've just switched to Firefox as Chrome keeps lagging. I'm running Fedora 31 and the latest version of Firefox 76.0.1.

When I use the 2 fingered scrolling and take my fingers off the touchpad, the page keeps scrolling until it slowly slows down and eventually stops or hits the end of the page. It doesn't then stop when I place my fingers back on the touchpad, so it just carries on regardless to another part of the page. It's ludicrous as it just goes past whatever I'm trying to look at! If I keep my fingers on the touchpad it stays put but as soon as I take them off, it's off on it's jollies again.

Is there anyway to disable this? I've unchecked smooth scrolling and autoscrolling. I've never had Firefox behave like this before on any Linux distro.

Asked by firefox739 12 ώρες πριν

Last reply by firefox739 7 ώρες πριν

Open the payload of a HTTP error

I'm a software developer working on backend services, always juggling between Firefox and Chrome (because none of them fully satisfy my needs). What I need from them is t… (διαβάστε περισσότερα)

I'm a software developer working on backend services, always juggling between Firefox and Chrome (because none of them fully satisfy my needs). What I need from them is to behave the way it will be most practical for me, which isn't necessarily aligned with the majority of users.

My current problem is this. I work with APIs which in my daily work often return various HTTP errors. These errors also contain a payload which describes the problem in detail. I want to be able to see this payload easily in the browser. Yes, I can use other tools like Postman for this (which I do), but for simple GET requests without special request headers it would be much more practical to just use a browser.

Currently, when my API opens an error (for example a 400 Bad Request), Firefox decides to just silently go back into the previous page (undos the URL change). If I open the Network tab in the Web Developer view, I can however see the failing response with all of its details. Still, this is too impractical for me.

BTW, the response contains a custom Content-Type which isn't recognized by Firefox by default. But Firefox isn't downloading the payload as a file (like it would usually do for a successful page load of an unknown Content-Type), it just silently doesn't do anything. I've installed an extension to handle my custom Content-Types (called "Open in Browser"), but since Firefox isn't attempting to open this one, I can't use it in this case.

So, how can I force Firefox to stay on that URL and show the response payload in the window? If not in vanilla Firefox, any plugins? I've already kind of spent too much time on this for my liking. :/

Asked by marko.vodanovic 14 ώρες πριν

Last reply by marko.vodanovic 12 ώρες πριν