gecko-dev

if someone has more details: I remember years ago that when I was digging FF source code I saw it was using chromium source code (not everywhere but for the CSS engine and extensions i think),that was the time servo was in consideration, is it still the case? I personally dont mind that I use both chromium + FF with some firewall rules but it always gave me impression that while FF using chromium source it does an advertise like completely different, isolated secure platform. Here is quick search just on "chrome" keyword on source code repo. https://github.com/mozilla/gecko-dev/search?q=chrome&unscope...

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] [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...

This is a pretty nice comment from the source that explains how it works: https://github.com/mozilla/gecko-dev/blob/11d9c7b7fa82fdfb8a... ``` // Recording and replaying works by controlling non-determinism in the browser: // non-deterministic behaviors are initially recorded, then later replayed // exactly to force the browser to behave deterministically. Two types of // non-deterministic behaviors are captured: intra-thread and inter-thread. // Intra-thread non-deterministic behaviors are non-deterministic even in the // absence of actions by other threads, and inter-thread non-deterministic // behaviors are those affected by interleaving execution with other threads. ```

In addition to what the other replies said, feel free to eyeball the code required to embed SpiderMonkey in Firefox at https://github.com/mozilla/gecko-dev/tree/master/dom/binding.... It's rather large and complex.

> but to my knowledge no browser implements it Firefox does, though I don't know how much they check beyond just the dNSName constraints. Here's the unit test making sure it stays working: https://github.com/mozilla/gecko-dev/blob/b8157dfaafc42deb3b...

https://github.com/mozilla/gecko-dev/commit/28fa74680f4a3d2c... I think they're using skia all the time since 2016.

Looking at the changeset [1], I'm curious why the explicit check for expiry (line 644/646) didn't work. Unfortunately the mentioned bug is rather light on details; presumably they were collaborating on IRC or something instead. [1] GitHub mirror to not stress their infra: https://github.com/mozilla/gecko-dev/commit/1d1260c7615f1d9a...

I wish someone from Mozilla or MS would comment on this, to be honest. Were they even considered? Historically, I've heard from various sources that Mozilla may not work at the same pace as some of the large corporations do in upstreaming patches and releases to the code base. This has (according to what I have heard, which may simply rest on rumor/speculation/heresey, mind you) kept a lot of large entities from getting on board. I've also heard that in building Quantum this is less of an issue, but their code base is a mess, and chromium's is incredibly well documented and clean by comparison. Anecdotally, I would be inclined to agree with my second statement up front, after just browsing the two, but please compare for yourself https://github.com/chromium/chromium https://github.com/mozilla/gecko-dev