Hello rf, indeed, didn't notice the bug before.
I opened an issue for that https://github.com/aaFn/Bookmark-search-plus-2/issues/101
and will look at correcting in 2.0.61.

Thanks aaFn.

Hello James Band, indeed you are not the first one asking for that.
I'll list it as a needed feature to come in a later release -> https://github.com/aaFn/Bookmark-search-plus-2/issues/100

Thanks, aaFn.

Hello Spiccico, explanation is in the add-on description, and in that page also -> https://github.com/aaFn/Bookmark-search-plus-2/wiki/Permissions-and-Privacy-policy

Firefox does not give access to its favicons database (the little image besides each bookmark), so the add-on has to fetch them one by one from the bookmarked URLs, on its first start and next ones, until they are all fetched.

If you do not want favicon fetching, and so do not want to have the images, simply disable favicon fetching in the add-on options page.

Of course, as soon as bug https://bugzilla.mozilla.org/show_bug.cgi?id=1315616 is corrected, I will modify the add-on to get the favicons from the FF internal DB, and there will be no more fetching.
Note: Chrome does give access to its favicon DB, but not Firefox today.

Meanwhile, once again, turn off the option if you do not want it.

I hope this clarifies, aaFn.

Hello sf, unfortunately, native theme details are not exposed to the add-on, or I didn't find how yet, although I searched for it ... If you find an add-on who is capable of reading the current theme and apply it, can you point it to me so that I can analyze how it does that ?

Now, I guess you're saying that somehow the theme you chose is imposing its value to the searchbox, preventing it from inheriting the body settings I made.
I tested the Dark theme under Windows and Linux, and nothing such as what you describe is happening = search box text is black as I specified.
=> would you be on IOS ? (I can't test it, I have none)

Probably better if you can open an issue so that I can track its details with you, if you agree -> https://github.com/aaFn/Bookmark-search-plus-2/issues

Note: in 2.0.57 I am forcing black on the search box, based on your feedback. I hope that will cure at least the visual problem and make it useable .. let me know. Thanks, aaFn.

Hello Giorgio, can you open an issue on https://github.com/aaFn/Bookmark-search-plus-2/issues with details of your Firefox version and conditions ?
The only case where it shouldn't work is with Firefox 56, because that Firefox version does not support the sidebar show/hide actions.

Thank you, aaFn.
-----------------------------------
Ok, glad it's resolved. Thank you for coming back here to say.
aaFn.

Hello blankon, would you be ok to open the things you see missing in https://github.com/aaFn/Bookmark-search-plus-2/issues
so that we can track there and align ?

Btw, to bookmark current tab, use the FF native Ctrl-D, and you can drag tabs and things to bookmark. If there is a bug, let's open that on GitHub to get that resolved.

Thank you, aaFn.

Hello Thomas, correct, this is the default behavior of FF -> https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/sidebar_action

This is a security default, so that an install doesn't go unnoticed by the user.

Note that:
- If you immediately redisplay the previous sidebar you had, then subsequent new windows use the one you just selected.
- When you close FF with a sidebar open, next time it restarts, it reopens with the same sidebar you had at time of close.
These are FF behaviors at this time which an add-on cannot modify.

Hello, thank you, I didn't know / didn't notice we could drag the URL address text from the location bar
=> usually, you just need to drag the (i) icon in the location bar ...
So I added it in 2.0.53 (which is out now).

On the 2 other points:
- Yes, upon first load, BSP2 has to fetch each bookmark URL to get its favicon, because the FF API doesn't make that available to add-ons. This is only on first load and until all bookmark favicons were fetched.
If you do not want that, just disable or pause favicon fetching in the options.

- "about:config" and in fact any "about:...." URL cannot be open by add-ons.
This is a security protection of FF (if you look at the browser console with Ctrl+Shift+J, you will see a security error), and this cannot be bypassed.

Hello, indeed ... This is a Firefox feature for add-on, not an add-on controllable thing, and this is missing.
I have opened a bug on FF for that -> https://bugzilla.mozilla.org/show_bug.cgi?id=1502713
.. waiting for it to be resolved (it is P3, so I do not expect it to be fast :-( )