This technical blog post advocates for developer empowerment and web accessibility through Firefox 70 features, emphasizing open access to technical education and secure development practices. Content demonstrates strong commitment to freedom of expression through knowledge-sharing and active participation in technical culture without access barriers.
The one thing that prevents me from switching to Firefox is the spell checker. Like many non-native English people, I'm constantly switching between languages when typing. Chrome is smart with that, and detects the right language sentence per sentence. Is there a way to have FF do this? Did I miss something?
Love Firefox. The philosophy, its snappiness, its many add-ons, the UI. - Glad to have an alternative to Chrome! Keep up the good work, Mozilla & Firefox team.
Wow, blown away by how much better the new password manager is! If they add support for custom fields on each login, this could almost completely replace my need for a 3rd party solution.
I noticed that firefox (dev edition) got rid of possibility to disable update notifications. I prefer my browser to be updated from repository rather than by itself. Did anyone has the same issue or found some workaround?
> Firefox 70 introduces three new properties related to text decoration/underline:
> text-decoration-thickness: sets the thickness of lines added via text-decoration.
> text-underline-offset: sets the distance between a text decoration and the text it is set on. Bear in mind that this only works on underlines.
> text-decoration-skip-ink: sets whether underlines and overlines are drawn if they cross descenders and ascenders. The default value, auto, causes them to only be drawn where they do not cross over a glyph. To allow underlines to cross glyphs, set the value to none.
I'm so excited for these. Implementing sane underlines for headers has been a pain in the ass for far too long. Writers rejoice!
The dev tool improvements all seem good. Still no support for inline code edits, which means JS debugging will still be something of a pain, but strengthening Firefox's position as one of the better tools for debugging and prototyping CSS.
I recently switched to firefox to give it a try. Does anyone else 2x-3x their video playback and notice the audio distortion in FF on mac? I've tried to find some discussion or workarounds for it, but no dice. Hoping that maybe the renderer in this release might help a little.
> Lastly, Core Animation allows us to move rendered content around in the window cheaply. This is great for efficient scrolling. (Our current compositor does not yet make use of this capability, but future work in WebRender will take advantage of it.)
Oh I am so excited about this! Where can I follow along with this development?
My message to the team would be: Please bring back the shader editor in devtools.
In a previous release, we had access to live reloading shader editor, which was really useful in my case, developing real time WebGL apps. It was a truly nice developer feature.
I am not a Firefox user but know that matching Webkit performance on macOS is going to be very hard.
So just fired a test on my Macbook Air - Safari 13 vs Firefox 70.
Opened top 10 links from techmeme. Both windows in background.
Firefox 70:
Energy use 30-200; CPU 20-25%; Threads 82
Safari 13:
Energy use 0.1-5; CPU 2-5%; Threads 11
If this is to celebrate I can only imagine what the things looked like before this release. Save for Apple fiddling with the energy use numbers (VW style) this means that my battery is going to last 4-5x longer with Safari. Can anyone replicate this for the sake of argument?
Firefox + Mozilla are awesome. I still have a Mozilla 1.0 t-shirt from the first release party!
I've recently seen a ton of FF fans state that the reason they love Firefox is that it doesn't have ads or track you and preserves your privacy.
However, Firefox wouldn't exist without Google and (to a lesser extent, Google Chrome).
They make 94% of their revenue via bundling and distribution deals with companies like Google.
So to say that Firefox doesn't really have ads I think it is a bit disingenuous. They don't have ads directly but they benefit directly from the ecosystem.
Without Google's ad business Firefox wouldn't exist.
Not saying this to be rude or call you guys out. I think we need an honest discussion on this issue.
Across the industry, we see users just outright refusing to pay for products because they're accustomed to 'free' being the norm.
News, social media, browsers, etc.
If you charge for a news site the users will revolt and go somewhere else.
If Facebook tried to charge users they would revolt.
Same thing for browsers.
Yet a large percentage of these same users will get angry and yell that they're privacy is being sold.
I'd rather things be direct. I'd rather we live in a world where customers paid directly for the product and I was the customer (not the product).
I recently tried Firefox again and I liked a lot. Only drawback for me at the moment is the lack of hardware video decoding on Linux. I hope it arrives soon.
Switching to CoreAnimation is very, very nice - however, this still doesn't feel quite at home on macOS because of a bug that's pretty old at this point.
Overflow/rubberband scrolling needs to be added here, because that is how scrolling is supposed to work on macOS. If you don't have it, you feel very alien. I'm not entirely sure why this isn't fixed after all these years, especially since Chrome managed to do it - it's not like an open source implementation doesn't exist at this point to crib the math from.
Mozilla won't quit - I love it. We need a third browser engine in the game and that should be sufficient as I've determined arbitrarily. There should be an open source browser that's a little more amateur and "democratically developed" than the big ones. Although browsers are approaching OSs in terms of complexity (or already there). Tried switching back to FF a while back but was still not as smooth as Chrome. I'll give it another shot. Good job, Mozilla!
Links for the password manager, "Firefox Lockwise" go through adjust, which appears to be a tracking/analytics/marketing platform. This is both through their website and by clicking through the Firefox UI menu.
I guess it's harder to walk the walk yourself when the desires to track usage and analytics come from within your own teams.
I use it to sync passwords with my phone. I like that I can use a fingerprint to unlock the file on my phone (instead of passphrase). I used to put silly passwords on sites I didn't care about (variants on a common password), but now I systematically generate a random password for all sites because there is no loss of convenience.
Weird, Chrome (specifically Electron) always gets confused when I speak English and Spanish all at once and Slack just starts to say everything I spell in English is wrong, it kinda annoys me. I don't think I have experienced this on Firefox.
> this means that my battery is going to last 4-5x longer with Safari
Well it might last 4-5x longer if you run safari in the background, since that is what you tested. But wouldn't the real test be running both browsers as the active window and comparing those results?
One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and windows to nearly zero. This is really good when running on battery because it is a shame to dedicate resources to things that aren't even visible on screen. But this could make the results far more dramatic through your test.
I would hypothesize that Safari still wins your performance test (if you were to re-test using them both as "active" windows), but probably not as dramatically as in the inactive window test.
> Without Google's ad business Firefox wouldn't exist
Really? My recollection of events 15 years ago is a little hazy, but wasnt FF a browser-only release of Mozilla, itself Netscape which has been around as long as time itself (~25 years?)
What are we talking about here? There was very definitely a push around 2003 to get FF adopted en masse, and I guess Google probably were a big factor in this ...
Bit of a stretch to say FF wouldn’t have existed otherwise though. There was very definitely some dissatisfaction across the board with IE dominance and its not hard to imagine something like FF being inevitable.
It'll be nice to simplify underline links tremendously once that becomes implemented in IE/Edge & Safari. The existing methods for avoiding underlines overlapping text descenders like Tufte-CSS's method (https://github.com/edwardtufte/tufte-css) are kinda crazy looking, and also cause the occasional bug with text highlighting.
> I've recently seen a ton of FF fans state that the reason they love Firefox is that it doesn't have ads or track you and preserves your privacy.
> However, Firefox wouldn't exist without Google and (to a lesser extent, Google Chrome).
These are unrelated issues, though. A connection, financial or otherwise, to Google, does not mean that users aren't getting a browser that prioritizes privacy.
Oh, please. You make it sound like Mozilla is equivalent to Facebook. Is that a smear campaign ?
You can donate to the Mozilla foundation. Have you ? Have you convinced your company or your friends to do so ?
Because that's a better alternative than outright singling Mozilla out for their ties to Google. Which last time I checked didn't make the user the product of Google like Chrome or Android does.
> I'd rather we live in a world where customers paid directly for the product and I was the customer (not the product).
Out of curiosity, what services and products are you paying for?
I'm willing to bet that a vast majority of HN users are still using a @gmail.com email address. And I'm actually in that super small minority that pays for services such as FastMail, Dropbox, Newsblur, 1Password, or YouTube (premium). I also donated to Mozilla among others.
---
The problem is that browsers should be part of the "commons", just like roads, since browsers are indespensible platforms in this day and age.
Are your taxes funding browsers? If no, then are you suggesting that only the privileged should have access to a good, modern browser?
---
Also products like Firefox are very unlike other products, because it's open source, both by license and by how it is developed. If Mozilla dies due to Google pulling the plug on their deal, Firefox is still open source and with enough resources somebody else can pick up its development.
To wit Thunderbird may still live under the Mozilla Foundation, but it is community driven, with donations from individuals being its primary source of funding. And it is moving along. Not as fast and it isn't as polished as its users would want, but it lives.
---
I'd rather use Mozilla's Firefox, instead of products with obscure VC-backed business models that just piggyback on top of Chromium and are thus in no way a threat to Chrome's monopoly.
IIRC Safari achieves this by suspending the processes in background tabs, which could be running inefficient JavaScript (polling for new ads etc). There's no cross-platform way to do this, but I think Mozilla absolutely need to try and find a way to address this. Web sites cannot be trusted to write efficient well-behaved JavaScript and so the burden of taming it falls upon the browser. There is probably some throttling going on, but clearly not enough. Running background JavaScript should be an opt-in permission, not the default.
On Windows I've been testing the new MS Edge because I've noticed my laptop has significantly higher CPU usage running FF. The reduced battery life is one thing, a hot laptop is another. Currently the new Edge is not as well optimized as the original, but there's more to come on that front.
I've been using FF since it was in beta, never left but I'm starting to come around to the reality that native browsers are best optimized for the device. While there's no real native browser to leverage on desktop Linux, on macOS/Windows, native may be the best way to go for most people. This is how break down browsers to friends and family.
Google Chrome- optimized for Google's needs and profit margin.
Microsoft Edge- optimized for your device, if running Windows.
Apple Safari- optimized for your device, if running macOS.
Mozilla Firefox- optimized for the user. Certainly a noble goal, but I increasingly have a "mobile" goal and that trend isn't slowing for anyone.
I just can't imagine Firefox will ever be performant as Safari. One is written for a single platform developed at the same company that develops the hardware and OS (I'm not trying to belittle the Safari team--it's kind of amazing what they do). The other is developed separately, must equally support at least 2 other OSes and has an expectation for supporting older setups.
My problem is that Safari won't work for me as a daily driver so it's not an option. It seems too aggressive in memory management and in reloading.
So I'm very happy to see Firefox improve performance over Firefox-v1.
With a previous update 1-2 years ago, the password manager seemed to lose the ability to force-create and edit new items, which is necessary if you are using it as a general purpose password manager, or for sites that stubbornly refused to play nice. I switched to LastPass, which worked out fairly well, with the family option, so that my spouse and I can share subsets of passwords with each other. But this FF update does look like they've fixed that issue.
Content extensively advocates for developer freedom, knowledge-sharing, and technical expression through detailed explanations of 16+ new Firefox capabilities, developer tools, and accessibility features. Editorial approach emphasizes open-source development culture and technical empowerment
FW Ratio: 57%
Observable Facts
Article provides detailed explanations of technical features (CSS properties, JavaScript methods, developer tools) with code examples and step-by-step guidance
Content is freely accessible on open blog without paywall, registration requirement, or access restrictions
Author is identified by name (Chris Mills) with full professional biography including employment history
Article includes multiple explicit calls to educational engagement: links to Firefox release notes, promotion of Mozilla Developer YouTube channel, and newsletter signup invitation
Inferences
Editorial approach advocates for developer empowerment and technical freedom as public goods worthy of investment and community participation
Open access structure demonstrates commitment to making technical knowledge and information freely available to all developers without economic or institutional barriers
Multiple content formats (blog, video, newsletter, documentation) reflect intentional design to support diverse learning pathways and information accessibility
Content explicitly advocates for technical education accessibility through multiple mechanisms: detailed explanations with concrete code examples, links to comprehensive documentation, promotion of YouTube educational channel, and newsletter signup. Editorial approach emphasizes making complex technical knowledge universally accessible
FW Ratio: 57%
Observable Facts
Article provides step-by-step technical explanations with concrete code examples for CSS properties, JavaScript methods, and developer tool usage
Content includes six explicit links to additional documentation and reference materials for deeper learning
Article prominently promotes Mozilla Developer YouTube channel: 'new Mozilla Developer YouTube channel will have videos covering many of the features mentioned below. Why not subscribe?'
Newsletter signup is featured with statement 'Sign up for the Mozilla Developer Newsletter' encouraging ongoing technical education
Inferences
Editorial structure is designed to support educational progression from overview summaries to detailed technical content
Multiple access points (blog post, YouTube, newsletter, documentation links, inline examples) demonstrate intentional commitment to making technical education accessible to learners with different preferences and backgrounds
Content advocates for free and open technical education as a public good and right of all developers
Content advocates for privacy-enhancing features, specifically secure password generation with Lockwise and Firefox Privacy Protection Report, framing these as beneficial advances for user security and control
FW Ratio: 50%
Observable Facts
Article lists 'secure password generation with Lockwise and the new Firefox Privacy Protection Report' as major release highlights in opening paragraph
Content explains HTML form implementation for secure password generation with developer guidance on autocomplete attributes
Inferences
Editorial framing positions privacy-protecting features as desirable improvements serving user autonomy and security
Content advocates for user control over password security as a rightful concern
Content promotes participation in web development technical culture by presenting new JavaScript internationalization methods, CSS features, and performance improvements as cultural and scientific advances. Framing celebrates technical progress and invites community engagement
FW Ratio: 50%
Observable Facts
Article presents new JavaScript methods (Intl.RelativeTimeFormat.formatToParts), CSS text-decoration properties, and performance improvements as technical advances worth sharing
Content explicitly invites community participation: 'share your constructive feedback' regarding new WebSocket inspector and 'Try it now, on a web page near you'
Inferences
Editorial approach frames technical innovation and feature development as cultural progress meriting celebration and community involvement
Content advocates for developers' participation in and contribution to advancing web development technical culture
Site implements Google Analytics and GTM tracking with UTM parameter removal utility, indicating awareness of privacy concerns but continued analytics deployment.
Terms of Service
—
Terms of service not observable in provided content.
Identity & Mission
Mission
+0.20
Article 19 Article 27
Mozilla's stated mission around open web and developer empowerment aligns with knowledge-sharing and technical security education.
Editorial Code
+0.05
Article 19
Technical blog format with clear author attribution and date stamps supports editorial transparency.
Ownership
+0.10
Article 19
Mozilla Foundation ownership as non-profit organization supports commitment to public interest over profit-driven content.
Access & Distribution
Access Model
+0.15
Article 26
Open access technical content published without paywall or registration barrier.
Ad/Tracking
-0.10
Article 12
Google Analytics and GTM tracking present on page reduces privacy score despite Mozilla's privacy advocacy.
Article published on open-access platform without paywall, login, or registration barrier; clear author attribution and professional presentation support freedom of information access
Site structure enables educational access through open publishing, multiple content formats without paywalls, clear learning progressions, and invitation to ongoing education through newsletter and video channels
Blog structure facilitates technical culture participation by publishing feature documentation, enabling community feedback, and providing engagement pathways through YouTube and newsletter channels
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 13:57:54 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.