The fact that this one then acknowledges that the bug is actually fixed if you use the browser in the recommended mode gives it extra points.
Furthermore, I never said "the entire project is shit". Firefox is a great piece of software, but I don't use it personally because of the issue I mentioned, among other issues in the same category (like the right-click menu looking different compared to other right-click menus, or not integrating with the macOS spell-check system).
Electrolysis isn't enabled by default
It is enabled by default, you just may have a plugin installed that is blocking it. The plugin(s) could be multiprocess compatible but unmaintained and missing the multiprocess=true flag in its package.json.You can go to about:support to see if multiprocess is truly enabled. If not, go to about:addons and start disabling extensions until it does work.
This seems to be the case because I downloaded Firefox 53 for the first time on my new MacBook Pro and e10s wasn't enabled. I had to go to about:config and enable it manually.
Firefox 54 has e10s-multi, with multiple web content processes.
If you go to about:support in your Firefox 53, the "Multiprocess Windows" item in the first section ("Application Basics") should tell you why e10s is disabled for you, if it's disabled.
Edit: Ah, so this is weird. It looks like e10s isn't enabled when you first run Firefox. You need to quit, and then relaunch. On the second launch e10s is then enabled. This explains why I thought it was disabled by default (since it was my first time running Firefox on this machine).
[0] https://gist.github.com/dstaley/b17ce52947cf520ca793d545daee...
I can't tell from over here what preferences you changed and in what order and when. You said "I had to go to about:config and enable it manually"... did you restart after that? e10s pref changes require a restart to take effect. What was the state of the preferences before you did that, if you remember?
In any case, glad to hear it's working for you now.
Considering stuff like Electron and co, that's not an unusual request.
I'd say the real way to look native in firefox involves XUL, even if it is getting removed.
Either you can build something looking native in the web languages, or Electron and co habe failed already.
Spoiler: it isn't.
This bug (and many others similar to it) are one of the main reasons I dislike using Firefox. It just feels out of place on macOS. I'm fine with non-native UI elements as long as they're not elements as fundamental as the select dropdown and the right-click menu.
Edit: Turns out this bug has been fixed, but only if you have Electrolysis [1] enabled [2].
[0] https://bugzilla.mozilla.org/show_bug.cgi?id=402625
[1] https://wiki.mozilla.org/Electrolysis
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=402625#c32