Great to see Mozilla consistently improving devtools in Firefox. I have been using them over Chrome for a while now, hope it gets to a place where most devs start using FF again for debugging web apps.
The CSS Changes page is a godsend. When editing CSS live it collects all the changes you've made so you can then go back and apply them in your codebase without having to hunt for them in the page elements.
> DevTools’ Network panel can now inspect WebSocket messages and automatically formats a variety of framework formats
Finally! This was the main reason to develop on Chrome instead of FF for me. The rest is almost comparable with Chrome DevTools for everyday web development.
Firefox is wonderful! Still hoping for much-needed general UI improvements, though. The tabs look bulky and have animation performance issues. The bookmarks manager is outdated and inconsistent with other tools in its look. Same with the downloads manager. All these things aren't a big deal, but Safari and Chrome seem to have a more pleasant overall graphic design.
Instead they seem to be making the UI worse. The new about:config seems to be a step backwards relative to the old text one (I particularly like that you cannot just browse, you have to know what you're looking for first).
was trying to find a bookmark recently, and seems I have 2 or 3 separate bookmarking systems, some here, some there, some from the menu bar, some from an icon.
Previously, "[f]or patent reasons, Firefox [did] not directly support MP3; instead, platform-native libraries [were] used to support MP3."[0] Now it uses ffvpx, which is their fork of ffmpeg. [1] [2]
Now if they could focus on native video decoding in Linux, something that actually works with Chromium and leads me to believe that Chromium developers are more committed to open source.
I've been shocked by how helpful the new Picture-in-Picture feature is. I wish the pop-out brought the full set of playback controls with it, but it's still far superior to making a full-blown window for video playback.
Sadly it's less than useful on MacOS (Still not stable, you have to manually turn it on in about:config). You cannot resize it, and it doesn't stay on top.
It's an interesting. In Chrome the way you can drag tabs out of the window and easily arrange youtube-tabs on the screen while they play works much smoother than in FF. But this new FF approach is kind of another way of solving that problem.
FF still causes considerable grief on my wife’s Windows 10 laptop. Two hour battery life is not acceptable. MS Edge (spit) more than triples that battery life.
I switch to Firefox few months ago on macOS and Linux. Other than issues on Youtube video playback ( sometimes the frame just freeze when I switch between different workspace in macOS )and a few minor bugs across google's service the overall experience is mostly on par with Chrome.
I'll update, because that's the sensible thing to do. But, frankly, I only use FF because the Zotero plugin works in it, but not in Safari.
And I tend to load FF, use it for a few minutes, and then quit it. That's because FF has a habit of going nuts somehow, and gulping energy on my OSX systems. I've no idea what causes the problem, and I don't really care, because Safari tends to be faster -- sometimes a lot faster.
[+] [-] pcx|6 years ago|reply
[+] [-] liminal|6 years ago|reply
[+] [-] cm-t|6 years ago|reply
[+] [-] fandaa|6 years ago|reply
Finally! This was the main reason to develop on Chrome instead of FF for me. The rest is almost comparable with Chrome DevTools for everyday web development.
[+] [-] weinzierl|6 years ago|reply
[+] [-] skykooler|6 years ago|reply
[+] [-] telegrammae|6 years ago|reply
[+] [-] m-p-3|6 years ago|reply
[+] [-] olah_1|6 years ago|reply
The fact that the tabs don't shrink, but instead slide out of view is infuriating. Something like this affects users constantly.
[+] [-] Someone1234|6 years ago|reply
[+] [-] senorjazz|6 years ago|reply
[+] [-] qxnqd|6 years ago|reply
What does "native" mean in this context? Uses accelerated CPU instructions? Uses the codecs of the system instead of something Firefox has built-in?
[+] [-] ihuman|6 years ago|reply
[0] https://developer.mozilla.org/en-US/docs/Web/Media/Formats/A...
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1582271
[2] https://github.com/mozilla/gecko-dev/blob/master/media/ffvpx...
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] techntoke|6 years ago|reply
[+] [-] portmanteaufu|6 years ago|reply
[+] [-] m-p-3|6 years ago|reply
[+] [-] s9w|6 years ago|reply
[+] [-] dickeytk|6 years ago|reply
[+] [-] psim1|6 years ago|reply
[+] [-] polymorph1sm|6 years ago|reply
[+] [-] bluenose69|6 years ago|reply
And I tend to load FF, use it for a few minutes, and then quit it. That's because FF has a habit of going nuts somehow, and gulping energy on my OSX systems. I've no idea what causes the problem, and I don't really care, because Safari tends to be faster -- sometimes a lot faster.
[+] [-] MrRadar|6 years ago|reply
[+] [-] techntoke|6 years ago|reply
[deleted]
[+] [-] benologist|6 years ago|reply
[+] [-] weinzierl|6 years ago|reply