I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
Firefox 70 released for Firefox Quantum: Developer Edition
91–100 of 116 posts
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#92Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.
I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/11661937700160798... Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#93Worth noting, this landed a patch that moves some of the UI work to Core Animation on MacOS[1]. More work will happen that builds on top of this, but some reports in that ticket are promising already. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1429522
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#94Earlier quoted context omitted.
Dev edtition gets the last nightly build two weeks before the same release hits Beta channel. One of the main changes for me as a Mac user is this: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32
Does this mean Firefox won't always be the "apps using significant energy" list?
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#95I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.
As others have pointed out, it may be worth looking into whether or not your reasons for using Chromium for the devtools are simply habit. Speaking for myself, I'm in the other camp. I never really ditched Firefox for Chrome except for a brief period[0]. I returned to Firefox back when it was still called "Firefox (Not Responding)". Other than the renaming (/s), it -- generally -- flies. The devtools do what I need t…
Main reasons were speed (Firefox opened slightly slower, and there seemed to feel like subtly more per-character latency typing in URL's) and minor anti-native behavior (the default-disabled-until-you-move-your-mouse Save button was particularly annoying, even though I understand the rationale).
I got the dreaded "Firefox process is already running" dialog a few times and had to close all my windows (ugh). I really missed Session Buddy; tried alternatives like Tree Style Tab but they weren't as clean.
Finally, one or two pages didn't render / operate properly (guessing due to non-cross-compatible JavaScript statement buried somewhere in them).
Unfortunately I don't have the time to create good step-by-step reproducibles and log bugs. I know some of this can be tweaked out via preference settings. I even spent some time tailoring my userChrome.css per suggestions here. But just couldn't get everything to work quite perfect. FF will have to spend some more time as my secondary browser, may give it a shot again in another year or so or next time Google pedals something stupid. Will try out the new devtools when I'm working on a page, maybe that'll be the hook for another attempt.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#96Earlier quoted context omitted.
No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...
Today updated to 70.b1, according to the About Firefox Developer Edition window. It has a "What's new" link next to the version number, but it links to a 404: https://www.mozilla.org/en-US/firefox/70.0beta/releasenotes EDIT - I put in a bug report on the release notes link, response says that release notes will come out next week
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#97Worth noting, this landed a patch that moves some of the UI work to Core Animation on MacOS[1]. More work will happen that builds on top of this, but some reports in that ticket are promising already. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1429522
Good work, and much appreciated!
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#98Earlier quoted context omitted.
The selection of the article itself is sufficient to add spin.
I don't think I understand.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#99Earlier quoted context omitted.
I don't think I understand.
Say Google makes a significant change to their ToS. If you link to the ToS, the title will be "Google ToS". So instead you are left with the option of linking to a Guardian/buzzfeed/wired blog post that is mostly fluff, doesn't include the actual ToS text in context, and has a hyperbolic headline. Which article you chose to post determines the spin.
Re: Firefox 70 released for Firefox Quantum: Developer Edition
#100Has there been a significant update to the devtools recently? I've been a devedition user for years, odd to see it on the front page of HN just linking to the homepage..
This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.