- If you do frontend work, our CSS grid inspector is unparalleled https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
- Firefox has built-in tracking protection (https://nakedsecurity.sophos.com/2017/11/12/firefox-to-offer...)
- Powerful add-ons like Tree Style Tab make managing large numbers of tabs much easier (https://addons.mozilla.org/firefox/addon/tree-style-tab/)
- Our WebAssembly performance tends to be better
- We should have better resource utilization when you have many tabs open
- You can mute audio on a page clicking the little speaker icon in the tab
If you want to contribute to the DevTools themselves, they're built using standard web technologies: HTML/JS, React/Redux, etc. https://github.com/devtools-html/
Although I don't know if chrome has this on by default nowadays as I turned it on so long ago.
But mute audio on per tab via speaker icon is available in chrome as well.
in chrome://flags/
* Tab audio muting UI control
If enabled, you can mute/unmute per tab via doing same thing.
Short of being able to optimize it soon, perhaps you could try buffering and displaying it at once. It would look less clunky and flimsy.
That said I'm giving FF57 a run as my main browser, will keep using Chrome Dev Tools for now.
Is there a way to selectively unblock certain trackers on a specific page?
I currently have the Tracking Protection set to Always and the block list on Strict. No problems yet, but I know there will be a few sites which won't correctly. Previously I always used Ghostery and there was a nice option to view exactly how many and which trackers were being blocked on each page. When viewing the blocked trackers, they could be selectively unblocked one at a time if required. This was handy to make some embedded video work, without necessary enabling Facebook tracking, which would occur if the whole page was unblocked.
(And I will have to find appropiate replacements for Leechblock and FireGesture)
https://addons.mozilla.org/en-US/firefox/addon/leechblock-ng...
Always watch where the incentives run, Chrome is for Google's best interests, not the web's and not the user's. Always has been and always will be because it's a for-profit organization.
I wish I had the time. So I'll have to wait for someone else to add the element DOM properties tab in thr panel that has the style rules and layout. Firebug had it, Chrome has it.
The right click and then Show DOM Properties with the results in the console pane is just painful to use.
https://superuser.com/questions/1261660/firefox-quantum-ver-...
(basically, hacking some CSS rules by creating a file in your AppData directory, so that the top bar is hidden)
Incidentally, I also discovered that Tree Style Tab's settings page under Firefox has a nice little box where you can configure the CSS it uses, which was nice because I prefer it with a smaller font and less padding.
In contrast, when you sign into Chrome, "Your experience in other Google products is personalized by including your Chrome history with your Web & App Activity."(https://support.google.com/chrome/answer/185277)
But if a substantial portion of Mozilla's funding comes from an organisation that does have a profit motive to monitor and monetise my activity on the web, then surely that's almost as bad (for me as the end user)?
Mozilla Corporation is wholly owned by the non-profit.
> both are open source
Not to the same degree, as Chrome != Chromium
Chrome is not open-source. Chromium is, but Chrome is not.
Tab containers are useful for having multiple accounts on the same site (Gmail/Github), or isolating work or most secure sites from regular browsing. The containers are more light-weight and more general than Chrome profiles (and they don't depend on having external accounts).
Pinned tabs don't close on Command+W. It's a small thing, but I kept accidentally closing my pinned tabs in Chrome.
Chrome Dev Tools are hard to beat, although Fx is slowly catching up there, too. I don't mind launching Chrome just for web dev.
They were! I think they've shrunk, though that might be an optical illusion... And I can't see a simple way to make them bigger (simple as in: not editing the css file).
Or the Sco Linux lawsuits.
https://blog.mozilla.org/blog/2017/11/14/firefox-features-go...
The real world is not Star Wars. For all the privacy considerations etc., this comment above reads extremely naive.