From 8eb497aa456c4bcf6cd4ccd12d68cdd86a60a7ae Mon Sep 17 00:00:00 2001 From: Daylin Cooper Date: Tue, 19 Mar 2024 01:32:47 -0700 Subject: [PATCH] Revise README to include basic troubleshooting guides --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 11592f3..528fe3d 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,14 @@ The only potential caveat: Widevine support. I don't know if this is controlled At the moment, it is required that you still manually disable non-native controls in order to use this. +## I installed this because of a theme, and I get an error! + +Here are some simple troubleshooting guidelines which fix 99% of reported problems: + +If the error mentions "**XULRunner**" and something about a **platform version mismatch**, then you need to download a version of this patch corresponding to your specific Firefox version. + +If the error says something about **XPCOM failing to initialise**, then it's most likely that you have a platform architecture mismatch. That means you're using a 32-bit version of Firefox. Mozilla just gives random 64-bit Windows users a 32-bit version for some reason, or at least I don't see any pattern. You can verify this quickly by seeing if Firefox is in "Program Files (x86)" instead of "Program Files". If you have a 32-bit version, then you just need to install the 64-bit version, which you can find on https://ftp.mozilla.org/pub/firefox/releases/ + ## Change documentation - [Scrollbars](docs/scrollbars.md) @@ -67,4 +75,4 @@ After building, the `xul.dll` file can be found in somewhere like `obj-x86_64-pc Also because Firefox uses Mercurial rather than Git, I found it would be more trouble than it's worth to attempt to post a modified codebase onto GitHub. I initially thought to fork [mozilla/gecko-dev](//github.com/mozilla/gecko-dev), but the commit identifiers for this repository do not at all align with their Mercurial revision identifiers, so it is less than worthless. Also, I found I couldn't even find certain tags which were useful to access in the Mercurial version. -As a result, I just `hg export` the patches I make, which makes them pretty easy to bring back into the codebase later. \ No newline at end of file +As a result, I just `hg export` the patches I make, which makes them pretty easy to bring back into the codebase later.