Pale Moon forum

If error handlers reported the name of the 'about:config' property that provoked the error, it would really help with troubleshooting. This is hopefully a very easy thing to implement.

Please consider it. - Mark.

um.. what? What exactly are you suggesting? Because I don't understand.

Moonchild wrote:um.. what? What exactly are you suggesting? Because I don't understand.

Hi MC. Thanks.

I get a timeout with some websites -- usually around 20 seconds. I don't know whether the http is stalled or dropped. I'd like to extend the time, but I don't know which about:config value to diddle. If the error handler disclosed that information, it would make diddling the value a lot easier. Otherwise, I have to guess based on property names, and that's not easy.

Warm Regards,
Mark.

I'm sorry but no. Websites timing out or any other "it doesn't work" scenario aren't simply 1:1 symptom -> cause relations (even though there are plenty of 1:1 cause -> symptom relations). Providing information about what's going on is one thing, but directing people to make changes in about:config on a "maybe it's caused by this" basis as directed by the software is just bad practice. People are already muddling in about:config more than they should as-is, no need to encourage it with wild guesses on error pages.

Moonchild wrote:I'm sorry but no.

I understand your concern.

Providing information about what's going on is one thing, ...

Just provide the cause of the error. Surely that's preferable to ignorance. Wouldn't you agree?

... but directing people to make changes in about:config on a "maybe it's caused by this" basis as directed by the software is just bad practice.

Then don't direct them. Simply making errors more informative doesn't direct anyone to do anything.

People are already muddling in about:config more than they should as-is, no need to encourage it with wild guesses on error pages.

Then don't encourage them. In fact, warning them would be appropriate. As it is now, changing settings is pure guesswork. Or, as an alternative, perhaps you could supply annotations for the settings in about:config so that adjusting them becomes less a matter of guesswork, eh?

Regards,
Mark.

PS: MC, I'd be happy to assist. I can read source, but will need help. Will you help?

Pretty much if it isn't general.useragent.override.[domain.tld] no user with rare exception should really be in about:config.

New Tobin Paradigm wrote:Pretty much if it isn't general.useragent.override.[domain.tld] no user with rare exception should really be in about:config.

Can you give that to me in English?

PS: Ah, I see (looking at 'general.useragent.override' in about:config). I can't believe anyone is still using browser-sniffing instead of DOM capabilities.

markfilipak wrote:.... Or... perhaps you could supply annotations for the settings in about:config so that adjusting them becomes less a matter of guesswork, eh?

I recommend the Config Comments extension. It puts comments from the source code to the side of settings in about:config.

markfilipak wrote:... I can't believe anyone is still using browser-sniffing instead of DOM capabilities.

Unfortunately, a lot of people are.

SpockMan02 wrote:I recommend the Config Comments extension. It puts comments from the source code to the side of settings in about:config.

I use the Config Comments extension. It's very sparse and often nonsensical. It didn't help me.

Well, as far as about:config goes, let me remind you: