Live data from Hacker News

Firefox 72.0

mozilla.org

541–543 of 543 posts

Re: Firefox 72.0

#541
post #294

Earlier quoted context omitted.

DevTools member here. We have been working on performance over the past release – is there anything specific that you can point out as being slower for us to focus on?

I have not yet tested v72, I'm on v71. The Chrome dev tools Console feels (not measured) about 100x faster then the Console in Firefox. Even Chromium Console can be limiting though. Yeh, I probably should not use console.logs for debugging, but it's much faster forkflow then firing up the debugger. Even with the lag. With the Chromium Console the lag is not that bad, and it has a search function. Both console's have…

I'm on v72 now and the Dev tools console feels even slower. It now freezes with just a few thousand log messages.

I also have to keep clicking the clear button to prevent the page from freezing if the dev tools console is open when loading the page.

Re: Firefox 72.0

#542
post #451

Earlier quoted context omitted.

Another front-end dev here. I tried to switch back from Chrome to Firefox, and while I was mostly impressed (especially devtools), I had a few gripes: - Dragging tabs didn't immediately drag out a window like in Chrome - A crashing tabs still seemed to crash/severely slow down the browser - Sluggishness in window opening / first open.

> [gripe:] - Dragging tabs [in Firefox] didn't immediately drag out a window like in Chrome Luckily (for me) this still holds and I see it as an advantage over Chrome; this pulling effect is amusing to look at (and I must admit that Chrome does great job when it comes to perceived speed and "snappiness" of it) but absolutely terrible feature when it comes to usability. For example it prevents transfer of tab between…

Hmm. I’d like the option. I use BetterSnapTool on Mac and very often tear off chrome tabs and immediately try to snap them to a side. This doesn’t work on Firefox.

Re: Firefox 72.0

#543

Earlier quoted context omitted.

This already happening for quite some time now. Many websites uses OneSignal and their fake prompt looks similar with Chrome's notification prompt (at least to ordinary users): https://documentation.onesignal.com/docs/permission-requests...

From this link: "OneSignal Prompts are a 'soft request', meaning that they are not invoking the 'hard request' of the browser's Native Permission Prompt. This is important because if a user denies the native prompt, the developer is unable to prompt the user again, unless the user goes through a multi-step process to re-enable these permissions. On the other hand, if a user dismisses a Soft Prompt, the app or website…

But it works on other people, which is why they bothered to create that in the first place.
Post reply on HN