Loading Profile...
javascript.options.showInConsole
Ubiquity seems to set 'javascript.options.showInConsole' to 'true' compulsorily at every startup (I'm not sure about other logging options). I feel this(these?) Pref should be left as default (false) in general use, to avoid message flood which are usually meaningless for users.
If it's mainly useful in development phase, I think that puttig such 'toggle' option in Command Editor Page may be better.
If it's mainly useful in development phase, I think that puttig such 'toggle' option in Command Editor Page may be better.
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?I'm not the one who did the hack, but I guess the intent was to ease the bug reporting process.
That is, with this pref turned on, we can just ask "What's in your error console?" -
Inappropriate?Yes, I agree to your guess.
But that scenario is not unique to Ubiquity. It can be applied to all addons, or all scripts for scriptable addons such as UserChrome.js, and so on -- but I believe they don't set the Pref compulsorily in user's environment.
What I want to point out is;
- There is NO choices for users to avoid this behavior.
Especially, even if user sets to false via about:config, it becomes true again and again on every startup.
(So I had to patch builtincmds.js and onstartup.js. I'm afraid when Ubiquity is integrated to Firefox...) - I believe this Pref (feature) is mainly provided for Developers, for their development/debugging environment.
(I think that's the reason why Firefox's default is false. Sorry if I'm worng) - It's also useful for troubleshooting on user's environment, but the frequency is rare (few percent ?) as compare with general usecases.
So I feel 'compulsive true (at every startup) on user's environment' is overdoing -- it's just my feeling.
Then,
- If enabling this Pref is very useful for not only rare case but also major use, Firefox's default value may be changed to true.
- If not, "user's choice" should be provided, such as:
put enable/disable option in Firefox's option dialog or Ubiquity's setup/development page.
Then the developer will ask user like "Enable this option, then what's in your console?"
Frankly speeking, I'm not sure the demerit about enabling this Pref... Does message flood occur ? Maybe developers will fix bugs (in their 'log enabling' environment) before the release. How about performance or memory footprint ? I don't know:-P maybe less effect ?
I'm only anxious, so I cannot request. But I hope Ubiquity team consider about this behavior when integrate to Firefox. - There is NO choices for users to avoid this behavior.
EMPLOYEE
