You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When switching from another application to Sublime Text by clicking on an editor window, it would be nice if the focus-triggering click could be ignored by Sublime Text. This would allow users to click anywhere in the window to focus the application without having to avoid click-sensitive areas that may not be fully visible (covered by another application's window), such as the sidebar.
Preferred solution
Several of the macOS applications I tested behave in this ignore-first-click way: Chrome, Safari, Firefox, Slack, Tower, Linear, Bitwarden, Music, and others. There is an important caveat: all of the browsers I tested process the first click if you click on a tab or in the address bar but ignore the first click if you click in the document area. (As a counterpoint, most built-in applications do process the first click, though notably not Safari.)
This behavior was accidentally present in the previous Sublime Text build (issue #6488). The referenced bug contains comments stating that intentional clicks to switch tabs were ignored, resulting in typing in the wrong file. This happened to me too and was jarring, but this could be mitigated by processing clicks on tabs and ignoring clicks elsewhere.
Alternatives
One alternative, though less desirable, would be to configurably ignore all application-focusing clicks, including on tabs. If this solution is explored, it would be helpful to disable all hover styles when the application is out of focus, to avoid giving the user the impression that the first click will be processed when in fact it will be ignored.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
But then build 4180 changed it so you had to focus the window in order to click the tabs. (I was ok with this change, but it took getting used to.)
Then build 4189 made it so the initial click to focus the window could change tabs or move the cursor in the open document. This second bit is really messing me up and I'm having a hard time adjusting because my cursor gets moved all the time now.
I strongly prefer the initial click to just focus the window and not change where the cursor position.
Problem description
When switching from another application to Sublime Text by clicking on an editor window, it would be nice if the focus-triggering click could be ignored by Sublime Text. This would allow users to click anywhere in the window to focus the application without having to avoid click-sensitive areas that may not be fully visible (covered by another application's window), such as the sidebar.
Preferred solution
Several of the macOS applications I tested behave in this ignore-first-click way: Chrome, Safari, Firefox, Slack, Tower, Linear, Bitwarden, Music, and others. There is an important caveat: all of the browsers I tested process the first click if you click on a tab or in the address bar but ignore the first click if you click in the document area. (As a counterpoint, most built-in applications do process the first click, though notably not Safari.)
This behavior was accidentally present in the previous Sublime Text build (issue #6488). The referenced bug contains comments stating that intentional clicks to switch tabs were ignored, resulting in typing in the wrong file. This happened to me too and was jarring, but this could be mitigated by processing clicks on tabs and ignoring clicks elsewhere.
Alternatives
One alternative, though less desirable, would be to configurably ignore all application-focusing clicks, including on tabs. If this solution is explored, it would be helpful to disable all hover styles when the application is out of focus, to avoid giving the user the impression that the first click will be processed when in fact it will be ignored.
Additional Information
No response
The text was updated successfully, but these errors were encountered: