firefox

Be that as it may, they can still roll out the passkey attestation requirement gradually, -- "flip the switch" just a few thousand users at a time -- so that at no one point in time is there a large blip in users. Truth be told, tech platforms don't even really need to measure what portion of users' devices support remote attestation, since the overwhelming majority of devices will support it. They just need to know that users are passkey-capable in the first place; once enough users have passkeys in any form, they can start requiring remote attestation. As for the browser permission prompt: Firefox simply warns you that the site is "requesting extended information about your security key [sic] which may affect your privacy." [1] It does not make it at all clear to the user that what's really happening is that the website is gating acces

Curiously, this makes Firefox display the default favicon (instead of no favicon): https://github.com/mozilla-firefox/firefox/raw/refs/heads/ma...

Interesting post, but I am surprised the author does not directly address Mozilla's own recent controversy regarding AI authorship of commits to the Firefox repo (https://github.com/mozilla-firefox/firefox/commit/71cc24b6a4...).

[4] looks like it's only a runner for the actual testing, which is a separate crate: https://github.com/mozilla/memtest (see: https://github.com/mozilla-firefox/firefox/blob/main/toolkit..., which points to a specific commit in that repo - turns out to be tip of main)

The simplest way to do this, what I believe memtest86 and friends do, is to write a fixed pattern over a region of memory and then read it back later and see if it changed; then you write patterns that require flipping the bits that you wrote before, and so on. Things like [1] will also tell you that something corrupted your memory, and if you see a nontrivial (e.g. lots of bits high and low) magic number that has only a single bit wrong, it's probably not a random overwrite - see the examples in [2]. There's also a fun prior example of experiments in this at [3], when someone camped on single-bit differences of a bunch of popular domains and examined how often people hit them. edit: Finally, digging through the Mozilla source, I would imagine [4] is what they're using as a tester when it crashes. [1] - https://github.com/mozilla-firefox/

Firefox has YouTube integration of course. Here's a Firefox file [1] specifically for integrating YouTube videos into their picture-in-picture system. Your random video website won't get this treatment of course, need to be a popular one. Here's a piece of C++ code [2] in the Firefox engine that specifically rewrites old YouTube embeds from their old HTML embed snippet to the new one. Again, your own video website will never be so deeply integrated into Firefox because it's not a top 10 website. Firefox Readability mode makes pages more readable by removing useless stuff like videos. Unless it's a YouTube [3] or other top-N popular video website of course. YouTube videos are given special treatment because it's popular and having small integrations like this make the user experience better. [1]: https://github.com/mozilla-firefox/firefox/

https://github.com/mozilla-firefox/firefox Rust isn't even mentioned in languages used.

Whoa... it looks like the Firefox HTML5 parser is still maintained as Java to this day! Here's the relevant folder: https://github.com/mozilla-firefox/firefox/tree/main/parser/... make translate # perform the Java-to-C++ translation from the remote # sources And active commits to that javasrc folder - the last was in November: https://github.com/mozilla-firefox/firefox/commits/main/pars...

https://github.com/chromium/chromium : C++ 74.0%, Java 8.8%, Objective-C++ 4.8%, TypeScript 4.2%, HTML 2.5%, Python 2.4%, Other 3.3% https://github.com/mozilla-firefox/firefox : JavaScript 28.9%, C++ 27.9%, HTML 21.8%, C 10.4%, Python 2.9%, Kotlin 2.7%, Other 5.4% How significant?

https://github.com/mozilla-firefox/firefox/blob/FIREFOX_143_... # Use 17 for Ctrl, 18 for Alt, 91 or 224 for Meta, 0 for none. - name: ui.key.accelKey type: uint32_t #ifdef XP_MACOSX value: 224 #else value: 17 #endif // user.js user_pref("ui.key.accelKey", 91);

Nope, as it turns out this was actually a thing until 2025-01-24, where a commit removed this "pretend to be Windows even on Linux platforms" behavior. https://github.com/mozilla-firefox/firefox/commit/eb2f90f870... This OS spoofing behavior was added in 2019-01-09 with this commit: https://github.com/mozilla-firefox/firefox/commit/264fe08c09... So Firefox has spoofed the User-Agent as a Windows machine on Linux for around 6 years, and only stopped doing it early this year. Would love to see whatever gaslit you into forgetting this easy to test and validate behavior.

See my comment (https://news.ycombinator.com/item?id=45644277) about Blitz. Perhaps you might be interested in collaborating :) Also, we're not using it in Blitz (although it could be added as a backend) but a note that WebRender is maintained. See Servo's most recent 0.68 branch (https://github.com/servo/webrender/tree/0.68) and also ongoing upstream development in the Firefox repository https://github.com/mozilla-firefox/firefox/tree/main/gfx/wr

> If Mozilla or Google were to make their code freely available on some git forge like GitHub https://github.com/mozilla-firefox/firefox https://github.com/chromium/chromium