How do I only show typed URLs in the Top Sites screen?
It's really obnoxious to see hundreds of ephemeral URLs that you'll never visit again on the Top Sites screen. Is there a way to make this user friendly so I can only see the URLs I typed. I am happy to set something in about:config.
الحل المُختار
Use about:config.
Set the following:
browser.urlbar.default.behavior
to 32. It uses a bitmask. So use can add the various values to get most any behavior you want.
See this page:
http://kb.mozillazine.org/Browser.urlbar.default.behavior
for an additional descriptions of this parameter.
This only seems to work on desktop version. Android Awful (Awesome) screen ignores this value.
Read this answer in context 👍 0All Replies (3)
الحل المُختار
Use about:config.
Set the following:
browser.urlbar.default.behavior
to 32. It uses a bitmask. So use can add the various values to get most any behavior you want.
See this page:
http://kb.mozillazine.org/Browser.urlbar.default.behavior
for an additional descriptions of this parameter.
This only seems to work on desktop version. Android Awful (Awesome) screen ignores this value.
Modified by jsheehy
Are you talking about the about:newtab page that shows (9) thumbnails of the most visited websites?
You can change the order of the boxes on the about:newtab page and drag them to a different position to pin them to that position or you can remove them by clicking the close X of an item to block them.
You can drag a bookmark or history item and drop them in a slot on the about:newtab page to pin them.
Changes are stored in the chromeappsstore.sqlite file in the Firefox Profile Folder under the pinnedLinks key and blockedLinks key.
No, this is for Android version. I would love to disable the stupid "Awesome" screen. The link you posted explained how to turn the tab garbage off on the desktop version, but Mobile (i.e. Android) version ignores the parameter value.
Likewise, the above "browser.urlbar.default.behavior" parameter set to '32' produces the reasonable behavior I want on the desktop, but the Mobile (Android) version just ignores this configuration parameter.