User.js stops processing after a line that isn't written correctly
I've created a new profile and migrated my user.js file and then I noticed that some of the preferences from that file didn't update in about:config and I've found out that was because I had those conflicting lines (the correct form is with quotation marks- "100 100"):
user_pref("full-screen-api.transition-duration.enter", "100 100"); user_pref("full-screen-api.transition-duration.enter", 100 100); user_pref("full-screen-api.transition-duration.leave", "100 100"); user_pref("full-screen-api.transition-duration.leave", 100 100);
Every line after that wasn't processed. (for example: user_pref("full-screen-api.warning.delay", 100);) And when I deleted the 2 lines that were written wrong everything else was processed.
All Replies (9)
The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers.
If you want to leave feedback for Firefox developers, you can go to the Firefox Help menu and select Submit Feedback... or use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.
If you want, you can file a bug report here; https://bugzilla.mozilla.org/
Oops my mistake :) I've sent a feedback now, thanks!
Don't forget to make a bug report.
Oh I didn't notice that because of the separating line, I'll do it now :)
You need the versions with the quotes around the values because this is a String pref.
- user_pref("full-screen-api.transition-duration.enter", "100 100");
- user_pref("full-screen-api.transition-duration.leave", "100 100");
You may have to reset prefs that do not work via the right-click context menu on the about:config page to the default value.
Note that it isn't guaranteed the the user.js file is processed when errors are present. It is up to you to make sure that all lines are correct.
Modified
cor-el said
You need the versions with the quotes around the values because this is a String pref.
Thanks but I already did it :) ("when I deleted the 2 lines that were written wrong everything else was processed.")
It's normal for Firefox to stop reading a user.js file once it see's an error or a conflict.
the-edmeister said
It's normal for Firefox to stop reading a user.js file once it see's an error or a conflict.
I think it shouldn't be normal. If it stops processing it should at least alert about it.
The Browser Console should be the place to report such an issue.
There is no need to create a bug report for issues (annoyances) like this as this will likely be marked as "WON'T FIX".