New tab page rows problem
Upon the update to the new Firefox Quantum 57.0, i immediately change the new tab page to the classic version as shown here (https://support.mozilla.org/pt-PT/questions/1183195). The problem is in the fact that whenever i restart the firefox, while the number of columns remains as i chose , the number of rows goes back to the default 3. Thank you
所有回复 (10)
Bumped. Isn't there anyone out there who knows how to fix this problem?
Show a screen of the error. I don't see the columns that your referring to.
WestEnd disse
Show a screen of the error. I don't see the columns that your referring to.
I change the number of rows from 3 to 4. When i close and then reopen the firefox, the number or rows is again 3.
If remember it is in one of these : USSER CHROME URL'S https://www.howtogeek.com/334716/how-to-customize-firefoxs-user-interface-with-userchrome.css/ http://techdows.com/2017/09/classic-theme-restorer-userchrome-css-modify-firefox-57-photon-ui.html https://github.com/Aris-t2/CustomCSSforFx/issues/1 https://www.accessfirefox.org/Theme-Font-Size-Changer.php https://www.userchrome.org/ https://www.accessfirefox.org/Firefox_Accessibility_Themes.php https://www.userchrome.org/what-is-userchrome-css.html http://kb.mozillazine.org/UserChrome.css https://github.com/axydavid/FirefoxUI/blob/master/README.md https://github.com/wilfredwee/photon-australis https://www.reddit.com/r/FirefoxCSS/ Note not all code in one place. Please let us know if this solved your issue or if need further assistance.
Firefox stores the changed value of browser.newtabpage.rows in the prefs.js file in your profile folder. Normally other software doesn't touch this file and your changes are retained indefinitely, unless you use the Refresh feature.
The following article lists some reasons for problems retaining changes in prefs.js, and also beware of external utilities that either clean up browser settings or protect against unwanted changes (they can't distinguish wanted from unwanted changes) such as Advanced SystemCare.
jscher2000 disse
Firefox stores the changed value of browser.newtabpage.rows in the prefs.js file in your profile folder. Normally other software doesn't touch this file and your changes are retained indefinitely, unless you use the Refresh feature. The following article lists some reasons for problems retaining changes in prefs.js, How to fix preferences that won't save
That didn't solve the problem. The strange thing is that when i change the number of columns and then quit/restart the firefox, the changes are still there. The same thing doesn't happen to the number of rows.
jscher2000 disse
The following article lists some reasons for problems retaining changes in prefs.js, and also beware of external utilities that either clean up browser settings or protect against unwanted changes (they can't distinguish wanted from unwanted changes) such as Advanced SystemCare. How to fix preferences that won't save
In the previews version of firefox i didn't have this problem.
Pkshadow disse
If remember it is in one of these : USSER CHROME URL'S https://www.howtogeek.com/334716/how-to-customize-firefoxs-user-interface-with-userchrome.css/ http://techdows.com/2017/09/classic-theme-restorer-userchrome-css-modify-firefox-57-photon-ui.html https://github.com/Aris-t2/CustomCSSforFx/issues/1 https://www.accessfirefox.org/Theme-Font-Size-Changer.php https://www.userchrome.org/ https://www.accessfirefox.org/Firefox_Accessibility_Themes.php https://www.userchrome.org/what-is-userchrome-css.html http://kb.mozillazine.org/UserChrome.css https://github.com/axydavid/FirefoxUI/blob/master/README.md https://github.com/wilfredwee/photon-australis https://www.reddit.com/r/FirefoxCSS/ Note not all code in one place. Please let us know if this solved your issue or if need further assistance.
Sorry, i tried use those links but i'm not that good at computers.
Wonder21 said
jscher2000 disseFirefox stores the changed value of browser.newtabpage.rows in the prefs.js file in your profile folder. Normally other software doesn't touch this file and your changes are retained indefinitely, unless you use the Refresh feature.
The following article lists some reasons for problems retaining changes in prefs.js, How to fix preferences that won't saveThat didn't solve the problem. The strange thing is that when i change the number of columns and then quit/restart the firefox, the changes are still there. The same thing doesn't happen to the number of rows.
In the previews version of firefox i didn't have this problem.
Now that I test it myself, mine behaves the same as yours. One typical workaround -- creating a text file in the profile folder named user.js in the profile folder with this line:
user_pref("browser.newtabpage.rows", 4);
-- doesn't have the anticipated effect of forcing the value.
When I look at the source code, the problem appears to be a "migration" feature which computes the number of "Activity Stream" top sites tiles by multiplying the browser.newtabpage.rows preference by 6. So most likely you have
browser.newtabpage.activity-stream.topSitesCount = 24
instead of the default value of 12. But the migratePref() function then resets the browser.newtabpage.rows value back to default. There's yer trouble.
I don't understand the code well enough to figure out whether there is a way to stop the migratePref() function from running.
Possible Workarounds
(A) Since the tiles "wrap" to fit the available space, can you work around this behavior by increasing browser.newtabpage.columns to multiply out to approximately the same number of tiles you wanted?
(B) Switch to using the New Tab Tools extension.
There is a bug on file for this, and one comment indicated that you can override the value reset by using an Autoconfig file to lock the preference.
https://bugzilla.mozilla.org/show_bug.cgi?id=1406088#c2
I added a comment to the bug with references to where it happens in the source code. Hopefully that will advance the ball.
See also:
- /questions/1194236 Changing number of rows in newtabpage doesn't work