gitkraken
Every time I open my IDE, focus is stolen by this extension
Description
Every time I open my IDE, focus is stolen by this extension
GitLens Version
latest
VS Code Version
No response
Git Version
No response
Logs, Screenshots, Screen Captures, etc
No response
And here I thought I was the only one with this issue, thanks for raising it @ramarivera
@ramarivera @brandonpapworth what view from GitLens takes focus? Can you provide steps for when this occurs?
- Open the IDE
- Try to do something
- Wait some seconds
- Your focus gets stolen because this tab gets focused
@ramarivera are you using GitLens in a container? The only time Home gets focuses is on new Installs.
Is there any more information you can provide -- like the exact set of steps. We can't reproduce this.
Do you have settings sync enabled in VS Code?
Can you also please enable debug logging by running the GitLens: Enable Debug Logging command from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens & GitLens (Git) channels in the Output pane.
Once enabled, please reproduce the issue, and attach the logs from the GitLens channel.
Thank you!
I encounter this as well, but I'm running on Nix so when I open VSCode it is effectively a new install every time. This may be different than @ramarivera's case.
The only time Home gets focuses is on new Installs.
Is it possible to disable this? Or is that default behaviour for extensions? GitLens is always the extension that steals focus, but I would understand if that was simply coincidental.
I've added a gitlens.advanced.skipOnboarding setting that you can set to avoid this and other "new user" experiences
Open Requirement in TestQuality
- Test Skip Onboarding in Sandbox with Pre-configured Setting.
- Test Default Behavior in Sandbox without Setting (Baseline).
- Test Multiple Sandbox Restarts with Setting Enabled.
- Test Setting via Workspace settings.json in Repository.
- Test GitLens Functions Work with Setting Enabled.
- Test Home View Accessible Manually with skipOnboarding.
- Test Welcome in SCM Grouped View Not Shown.
- Test Setting via VS Code Settings UI.
- Test Debug Logging for Onboarding Flow.
- Test Mixed Environment - Sandbox and Regular VS Code.
- Test Performance on Sandbox Cold Start.
- Test Different Sandbox Environment Types.
- Test Upgrade from Previous Version with Setting.
- Test Walkthroughs Not Shown with Setting Enabled.
- Test Runtime Setting Change - Enable skipOnboarding.
- Test Runtime Setting Change - Disable skipOnboarding.
- Test Multiple Workspace Folders in Sandbox.
- Test User Settings vs Workspace Settings Priority.
- Test Welcome Content Conditions in contributions.json.
- Test Storage Handling with skipOnboarding.
