搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Bookmarks Disappear When Clicked On

  • 2 个回答
  • 0 人有此问题
  • 12 次查看
  • 最后回复者为 zeroknight

more options

I'm on MacOS Sonoma 14.0. Since the Firefox update to v. 119.0, I have had a really strange issue which is hard to describe, but I'll try.

In the Bookmarks Sidebar, whenever I click a folder, it disappears from view leaving a blank, empty space. The folder is still there, and everything in the folder is visible, but the folder itself is just a blank space. When the blank space is clicked on, the folder reappears and can still be selected, but the folder beneath it becomes invisible. It is almost as though the background and the foreground text and folder outline are the same color. The same thing occurs with History. The bookmarks themselves never become invisible, just the folders.

Has anyone seen this behavior? Does anyone have any idea how to fix it?

Thanks.

I'm on MacOS Sonoma 14.0. Since the Firefox update to v. 119.0, I have had a really strange issue which is hard to describe, but I'll try. In the Bookmarks Sidebar, whenever I click a folder, it disappears from view leaving a blank, empty space. The folder is still there, and everything in the folder is visible, but the folder itself is just a blank space. When the blank space is clicked on, the folder reappears and can still be selected, but the folder beneath it becomes invisible. It is almost as though the background and the foreground text and folder outline are the same color. The same thing occurs with History. The bookmarks themselves never become invisible, just the folders. Has anyone seen this behavior? Does anyone have any idea how to fix it? Thanks.

所有回复 (2)

more options

I just tried changing themes. I was using the "Light" theme. When I change to any other theme, the problem goes away. I therefore believe my supposition that perhaps the foreground/text color for selected items is the same as the background color in this "light" theme.

more options

This should be fixed by Bug 1861669 which is currently in Beta 120.