logseq / logseq

A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: http://trello.com/b/8txSM12G/roadmap
https://logseq.com
GNU Affero General Public License v3.0
30.26k stars 1.77k forks source link

Unexpected behaviour when trying to click in the Search icon #11291

Open oscaretu opened 3 weeks ago

oscaretu commented 3 weeks ago

Search first

What Happened?

Unexpected behaviour when trying to perform a search

Sometimes when I try to start a search by clicking on the search icon, the icon does not usually obey. I have to make multiple clicks until I get the popup with the search box to show up.

While looking for a way to reproduce the problem, I think I have found the conditions that cause the click to fail: when the Logseq window is maximised, the search facility is only activated when the mouse pointer is positioned at the bottom of the ‘box’ containing the magnifying glass icon (perhaps the mouse pointer has to be in the bottom 25% of the magnifying glass icon for it to be activated)

Even if the Search icon is not active, the keyboard shortcut (CTRL + k) allows you to activate the search popup.

Reproduce the Bug

  1. Maximise the Logseq window.
  2. Move the mouse pointer, starting from the edge of the Logseq window, starting at the top vertical of the magnifying glass icon, slowly moving the mouse pointer, slowly, downwards. When you are approximately in the bottom 25% of the magnifying glass icon box, the icon is activated.

Expected Behavior

Clicking in any point of Search icon should activate the Search popup

Screenshots

imagen

Desktop or Mobile Platform Information

App Version: 0.10.9 Git Revision: c67b8b5 Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.9 Chrome/118.0.5993.159 Electron/27.1.3 Safari/537.36 Language: es Plugins: logseq-anki-sync (v6.0.1), logseq-bullet-threading (v1.1.4), logseq-journals-calendar (v0.10.10), logseq-tabs (v1.19.4)

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.