Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Linux: Bookmark button not clickable for seconds after starring a page

  • 3 odpowiedzi
  • 1 osoba ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od cor-el

more options

On Linux, after bookmarking a page with star, clicking the bookmark button is not possible for 1-2 seconds. Since the bookmark dialogue is pretty bad (Why can't I edit the URL? Why can't I add keywords?), I often have to edit the bookmark afterwards. This however is not possible for some time after starring, because the button is not responding.

What's up with the click delay and how do I change it?

On Linux, after bookmarking a page with star, clicking the bookmark button is not possible for 1-2 seconds. Since the bookmark dialogue is pretty bad (Why can't I edit the URL? Why can't I add keywords?), I often have to edit the bookmark afterwards. This however is not possible for some time after starring, because the button is not responding. What's up with the click delay and how do I change it?

Wszystkie odpowiedzi (3)

more options

You need to edit the URL via the right-click context menu in the Properties of a bookmark. You can do this on the Bookmarks Toolbar and in the sidebar and in the Bookmarks Manager (Library).

If Firefox in unresponsive after you have clicked the star then there might be a problem with the places.sqlite database or with an extension.

If you use Sync then best is to disconnect Sync temporarily during troubleshooting.

You can check for problems with the places.sqlite database (bookmarks and history) in the Firefox profile folder.

  • use "Verify Integrity" button on the "Help -> Troubleshooting Information" (about:support) page
    in case errors are reported close and restart Firefox and retry

See also:

If "Verify Integrity" button on the "Help -> Troubleshooting Information" (about:support) page cannot repair places.sqlite then remove all places.sqlite files in the Firefox profile folder. Firefox will rebuild places.sqlite and restore the bookmarks from a recent JSON backup in the bookmarkbackups folder.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

Thank you, I know how to edit bookmarks. This doesn't change the fact that the bookmarking dialogue is bad though.

And there are no extensions interfering with the places database. First, I don't have many installed. Second, it happened before installing most of them (with only uBlock Origin installed). Third, it also happens in private windows where extensions are disabled. Fourth, I even tried it in a fresh profile without anything changed from the defaults and the delay is still there.

I'm pretty sure the delay is some GUI "feature" that shouldn't be there.

more options

It is possible to use code in userChrome.css to have the location field and the keyword visible all the time althouh you will have to be aware that these fields are also visible when they do not apply (e.g. a folder).

You can add code to the userChrome.css file below the default @namespace line.


@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* only needed once */

/* Bookmark This Page edit panel */
#editBMPanel_locationRow, #editBMPanel_keywordRow {
 visibility:visible!important;
}

/* Hide Giant Thumbnail and Favicon */
*|div#editBookmarkPanelFaviconContainer,
#editBookmarkPanelFaviconContainer,
#editBookmarkPanelImage {
 display: none !important;
}

You need to create the chrome folder (lowercase) in the <xxxxxxxx>.default profile folder if this folder doesn't exist.

  • use a plain text editor to create a (new) <buserChrome.css</b> file in the <i>chrome folder (file name is case sensitive)
  • paste the code in the userChrome.css file in the editor window
  • make sure the userChrome.css file starts with the default @namespace line

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.