starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Word Not Snipping windows terminal properly #15098

New Issue
Closed
opened 2026-01-31 04:28:28 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 04:28:28 +00:00
Owner
Copy Link

Originally created by @mehulminat on GitHub (Sep 5, 2021).

Windows Terminal version (or Windows build number)

10.0.19041.1110

Other Software

Word 2019 Pro Plus

Steps to reproduce

Open a word document and try to add photo using Insert-> screenshot.
It will be showing a preview of grayed screen .
image

Expected Behavior

It was expected to show the contents of that specific terminal chosen including the text . Like it word with any other window

Actual Behavior

It just snipped gray window.
image

But manual snipping using snip tool is working perfectly fine.

Originally created by @mehulminat on GitHub (Sep 5, 2021). ### Windows Terminal version (or Windows build number) 10.0.19041.1110 ### Other Software Word 2019 Pro Plus ### Steps to reproduce Open a word document and try to add photo using Insert-> screenshot. It will be showing a preview of grayed screen . ![image](https://user-images.githubusercontent.com/72225679/132140789-aa2306f9-3a4e-49b8-b501-58f4dadcf4ec.png) ### Expected Behavior It was expected to show the contents of that specific terminal chosen including the text . Like it word with any other window ### Actual Behavior It just snipped gray window. ![image](https://user-images.githubusercontent.com/72225679/132140842-8dcf23f8-11c2-4499-9570-5cf53e8b6aa1.png) But manual snipping using snip tool is working perfectly fine.
claunia added the Needs-TriageResolution-External labels 2026-01-31 04:28:28 +00:00
claunia commented 2026-01-31 04:28:29 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 6, 2021):

This issue manifest in other MS Office products. I tried Excel & PowerPoint and the content of WT is not showing when using "Insert->Screenshot->Available Windows" option. It grabs the content of a PowerShell session, the old style not launched in a WT session.

However, this issue seems to be more than what was reported by mehulminat. In World no content from other application is being inserted by this method. Trying a screenshot from Chrome browser it resulted in a gray box inside the document. Maybe this should be a MS Office bug.

@elsaco commented on GitHub (Sep 6, 2021): This issue manifest in other MS Office products. I tried Excel & PowerPoint and the content of WT is not showing when using "Insert->Screenshot->Available Windows" option. It grabs the content of a PowerShell session, the old style not launched in a WT session. However, this issue seems to be more than what was reported by mehulminat. In World no content from other application is being inserted by this method. Trying a screenshot from Chrome browser it resulted in a gray box inside the document. Maybe this should be a MS Office bug.
claunia commented 2026-01-31 04:28:29 +00:00
Author
Owner
Copy Link

@mehulminat commented on GitHub (Sep 6, 2021):

However, this issue seems to be more than what was reported by mehulminat.

Yes , this seems to be an bug with MS Office Products because it can't grab Calculator and many other window but successful in grabbing cmd, powershell , controlpanel, windows explorer

@mehulminat commented on GitHub (Sep 6, 2021): > However, this issue seems to be more than what was reported by mehulminat. Yes , this seems to be an bug with MS Office Products because it can't grab Calculator and many other window but successful in grabbing cmd, powershell , controlpanel, windows explorer
claunia commented 2026-01-31 04:28:29 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 7, 2021):

This is an issue with UWP, which WT pretends to be. (Technically WT is Win32 with a UWP wrapper). I'd file a suggestion in Feedback Hub for each of the Office products requesting this support be added. I'm pretty sure they all use the same code for this, so a change in one product hopefully makes it to the others.

@WSLUser commented on GitHub (Sep 7, 2021): This is an issue with UWP, which WT pretends to be. (Technically WT is Win32 with a UWP wrapper). I'd file a suggestion in Feedback Hub for each of the Office products requesting this support be added. I'm pretty sure they all use the same code for this, so a change in one product hopefully makes it to the others.
claunia commented 2026-01-31 04:28:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 7, 2021):

This is an issue with UWP, which WT pretends to be. (Technically WT is Win32 with a UWP wrapper

Lets just stop using these terms, because they frankly don't reflect the state of Windows in 2021. The Terminal is a Windows application that uses XAML. Win32 and UWP are just subsets of the Windows API.

My guess would have been that Office is having troubles with things that render with DX to a swapchain, but if they're having troubles with Calculator as well, then they might just have problems with all XAML applications. I don't see anything about it on the WinUI repo though...

@zadjii-msft commented on GitHub (Sep 7, 2021): > This is an issue with UWP, which WT pretends to be. (Technically WT is Win32 with a UWP wrapper Lets just stop using these terms, because they frankly don't reflect the state of Windows in 2021. The Terminal is a Windows application that uses XAML. Win32 and UWP are just subsets of the Windows API. My guess would have been that Office is having troubles with things that render with DX to a swapchain, but if they're having troubles with Calculator as well, then they might just have problems with all XAML applications. I don't see anything about it on the WinUI repo though...
claunia commented 2026-01-31 04:28:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2022):

Filed this on Office to start the discussion. For my own notes, the string fdcl_v4_eb5f5d37884552d38d2fe68af744570b should return exactly one email in my inbox.

There's likely nothing for us to do on our end here, other than apply pressure where possible. For janitorial purposes, I'm gonna close this one out. Thanks!

@zadjii-msft commented on GitHub (Feb 17, 2022): Filed this on Office to start the discussion. For my own notes, the string `fdcl_v4_eb5f5d37884552d38d2fe68af744570b` should return exactly one email in my inbox. There's likely nothing for us to do on our end here, other than apply pressure where possible. For janitorial purposes, I'm gonna close this one out. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15098
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?