| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 26 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 13:56:12 |
| Calls: | 629 |
| Files: | 1,186 |
| D/L today: |
18 files (29,890K bytes) |
| Messages: | 165,845 |
firefox 143.0.3-a Windows 10 64 bit
I don't know what setting I could have changed, but I am not able to
access sites like this <https://www.gaiagps.com/map/> or this <https:// wingis.org/maps/propertySearch> without getting the browser doesn't
support WebGL 2 message.-a If I go into troubleshoot mode upon restart it works again and does load the maps.-a The only extension I am using is uBlock Origin.-a Disabling it alone does not change anything and the
pages won't load.-a So it must be some setting I have changed recently.
Anyone have an idea where to look or how to pinpoint the precise failure spot?-a I guess I"m going to have to go into the config files and look
for a recent change somehow.-a I often take some of the tips from this
group and implement them, but apparently one of them must have done
this.-a If I figure it out, I will let you know.
Anybody else not able to access those pages?
Now that it is working again, I also believe that this happened before
and I found this same fix for my system. I'm 99.9% sure I've done this before. So I guess an upgrade must have changed this back to the
default setting. I hope I remember this next time, but I'll keep a copy
of this which I'll probably forget all about when it happens again.
Now that it is working again, I also believe that this happened before
and I found this same fix for my system. I'm 99.9% sure I've done this before. So I guess an upgrade must have changed this back to the
default setting. I hope I remember this next time, but I'll keep a copy
of this which I'll probably forget all about when it happens again.
Easy way to keep all important settings you altered: a "user.js" file.
If you haven't already one, create it (plain text file) in your profile(s) right where "prefs.js" already resides.
The settings in there override the settings in the "prefs.js" and you
can copy the "user.js" to all FFs you use.
Easy way to keep all important settings you altered: a "user.js"
file.
sticks wrote:
[..snip..]
Now that it is working again, I also believe that this happened before
and I found this same fix for my system. I'm 99.9% sure I've done this
before. So I guess an upgrade must have changed this back to the
default setting. I hope I remember this next time, but I'll keep a copy
of this which I'll probably forget all about when it happens again.
Easy way to keep all important settings you altered: a "user.js" file.
If you haven't already one, create it (plain text file) in your profile(s) right where "prefs.js" already resides.
The settings in there override the settings in the "prefs.js" and you
can copy the "user.js" to all FFs you use.
[If you delete "user.js" the according settings in "prefs.js" aren't
reset! You would have to do this manually.]
So in your case the appropriate lines for performance settings and
hardware acceleration from the settings pane would be in "user.js":
user_pref("browser.preferences.defaultPerformanceSettings.enabled", false); user_pref("layers.acceleration.disabled", true);
HTH
Frank Miller wrote:
[..snip..]
Easy way to keep all important settings you altered: a "user.js" file.
If you haven't already one, create it (plain text file) in your profile(s) >> right where "prefs.js" already resides.
The settings in there override the settings in the "prefs.js" and you
can copy the "user.js" to all FFs you use.
P.S.: no update will ever touch or alter this "user.js" file.
On Thu, 2 Oct 2025 03:31:32 +0200, Frank Miller wrote:
Easy way to keep all important settings you altered: a "user.js"
file.
I was looking for info on this, and found <https://kb.mozillazine.org/User.js_file>. It appears user.js is a
settings override, such that any changes made to the same settings via about:config become temporary, only in effect for the current session,
and revert to the user.js values when you restart Firefox.
This may or may not be what you want.
On 10/1/2025 8:34 PM, Frank Miller wrote:
P.S.: no update will ever touch or alter this "user.js" file.
I was aware of this, but it does beg a question. I do have and use a firefox account, and sync three different machines. This is probably
the oldest and I think my newer machine doesn't need this because it has better hardware and I tested it after I had made this change, though I
did not check to see if the same changes were in that box. I'll have to
do that. I am guessing changes like this, or a user.js file, is not something that gets synced and can be different for each machine? You
know if this is correct?
sticks wrote:
On 10/1/2025 8:34 PM, Frank Miller wrote:
P.S.: no update will ever touch or alter this "user.js" file.
I was aware of this, but it does beg a question. I do have and use a
firefox account, and sync three different machines. This is probably
the oldest and I think my newer machine doesn't need this because it has
better hardware and I tested it after I had made this change, though I
did not check to see if the same changes were in that box. I'll have to
do that. I am guessing changes like this, or a user.js file, is not
something that gets synced and can be different for each machine? You
know if this is correct?
I've only tested FF sync a long time ago and found out it wasn't useful
for me. So i don't have an answer for that. Maybe you can just test that
one time and compare the different "prefs.js" files.
But as i said, the contents of "user.js" are written to "prefs.js" and executed every time FF starts. So when you sync also your preferences
i think these altered settings are synced also.
On 10/1/2025 9:54 PM, Frank Miller wrote:[..snip..]
sticks wrote:
[..snip..]I am guessing changes like this, or a user.js file, is not
something that gets synced and can be different for each machine? You
know if this is correct?
But as i said, the contents of "user.js" are written to "prefs.js" and
executed every time FF starts. So when you sync also your preferences
i think these altered settings are synced also.
OK. I'll have to do some testing then, because I can see how the answer
to this question is important for many possible things for people who do sync their different machines. Thank you.
On 10/1/2025 9:54 PM, Frank Miller wrote:
sticks wrote:
On 10/1/2025 8:34 PM, Frank Miller wrote:
P.S.: no update will ever touch or alter this "user.js" file.
I was aware of this, but it does beg a question.-a I do have and use a
firefox account, and sync three different machines.-a This is probably
the oldest and I think my newer machine doesn't need this because it has >>> better hardware and I tested it after I had made this change, though I
did not check to see if the same changes were in that box.-a I'll have to >>> do that.-a I am guessing changes like this, or a user.js file, is not
something that gets synced and can be different for each machine?-a You
know if this is correct?
I've only tested FF sync a long time ago and found out it wasn't useful
for me. So i don't have an answer for that. Maybe you can just test that
one time and compare the different "prefs.js" files.
But as i said, the contents of "user.js" are written to "prefs.js" and
executed every time FF starts. So when you sync also your preferences
i think these altered settings are synced also.
OK.-a I'll have to do some testing then, because I can see how the answer
to this question is important for many possible things for people who do sync their different machines.-a Thank you.