Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert falsy tooltip change #843

Merged
merged 1 commit into from
Feb 2, 2021
Merged

Revert falsy tooltip change #843

merged 1 commit into from
Feb 2, 2021

Conversation

bwateratmsft
Copy link
Contributor

Reverts #841, fixes #842. The upstream VSCode issue has been fixed so we should go back to our old behavior.

@bwateratmsft bwateratmsft requested a review from a team as a code owner February 1, 2021 15:30
@bwateratmsft
Copy link
Contributor Author

bwateratmsft commented Feb 1, 2021

Before submitting this I'd like to verify the fix in tomorrow's Insiders build.

UPDATE: Verified the fix!

@ejizba
Copy link
Member

ejizba commented Feb 1, 2021

Can you comment on the timing of this? When was the bug introduced in VS Code and when was it fixed? Are we at risk of people on older versions of VS Code still seeing the bug? If so, it doesn't seem that bad to leave the workaround in

@bwateratmsft
Copy link
Contributor Author

@ejizba the bug was introduced in Insiders 1.53 late last year and just fixed yesterday; it hasn't appeared in any GA builds of VSCode yet. So, removing the fix (i.e. submitting this PR) should be fine, since it would only affect a few folks on Insiders until they upgraded.

@bwateratmsft bwateratmsft merged commit efd1c8f into main Feb 2, 2021
@bwateratmsft bwateratmsft deleted the bmw/revertFalsyTooltip branch February 2, 2021 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Revert falsy tooltip change (#841)
2 participants