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

Windows API GetConsoleScreenBufferInfo() does not return expected values #18407

Closed
DKBS13 opened this issue Jan 7, 2025 · 2 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@DKBS13
Copy link

DKBS13 commented Jan 7, 2025

Windows Terminal version

Windows Console Host

Windows build number

No response

Other Software

No response

Steps to reproduce

In windows 11 console host (not windows terminal), F11 go to full screen, Use CTRL+Mouse Wheel zoom in/out, there is an issue: Windows API GetConsoleScreenBufferInfo() returns realtime dwSize and srWindow values, not following windows font scaling operation. F11 again, the expected values have returned.

Expected Behavior

GetConsoleScreenBufferInfo() return realtime values

Actual Behavior

GetConsoleScreenBufferInfo() return old values until hit F11 key

@DKBS13 DKBS13 added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 7, 2025
@carlos-zamora
Copy link
Member

Thanks for filing! What windows build are you using /?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Jan 22, 2025
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

2 participants