[Solved] Bookmarks sidebar search: clear-search icon disappears when I need it the most
When I open the bookmarks sidebar, the search entry box shows an icon to clear the input. Yet, as soon as I type something in the appropriate input box, this icon dissappears from view and I have to resort to manually using the backspace key to make edits. Not the biggest of deals, I do realize that, but still irritating, as I have loads of bookmarks, hence I use the search facility very often.
Personally I find the 'logic' to be reversed here (but I also sleep during the day and work during the night, so it might just be me...). It just doesn't make much sense: when there's nothing to clear the icon in question is visible, when there is something to clear it's not.
I've tried reversing this behavior via the userChrome.css file without succes:
.textbox-input .textbox-search-clear {
visiblity: collapsed !important;
}
.textbox-input[selected="true"] .textbox-search-clear {
visiblity: visible !important;
}
doesn't change anything, so I guess these are the wrong selectors in this context.
Is there a way to achieve what I'm looking for via this CSS file or do I need to look elsewhere?
由glitsj16于修改
所有回复 (3)
glitsj16 said
Personally I find the 'logic' to be reversed here ...
It seems like the behavior is currently reversed for some reason - the X on the right should only be visible when you start typing, but not yet when opening the sidebar and the field is still empty.
Are you sure there is no CSS code to remove somewhere instead?
Did you try the behavior in Safe Mode and/or in a clean profile?
Are you using a dark theme or a light theme in case Firefox doesn't detect this properly and the icon has the same color as the background?
Does it work if you select a light theme?
Can you attach a screenshot?
- https://support.mozilla.org/en-US/kb/how-do-i-create-screenshot-my-problem
- use a compressed image type like PNG or JPG to save the screenshot
选择的解决方案
Tonnes said
Are you sure there is no CSS code to remove somewhere instead?
Please ignore, issue is solved. I indeed had erroneous code in userChrome.css causing the (non-)issue.