Progress bar causes display issues when in debugger

[ThomasNieto]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

I am trying to debug a module and if a progress bar is present when the debugger is entered it causes display issues by being always present at the bottom of the prompt. You can also see that the curser is on the same line as the and when text is typed it writes over the progress bar. Maybe the progress bar should be hidden when the debugger is displayed or detached from the bottom of the prompt.

Expected behavior

The progress bar does not causes display issues with the prompt.

Actual behavior

The progress bar stays at the bottom of the interactive prompt and causes display issues.

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.4
PSEdition                      Core
GitCommitId                    7.2.4
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

[PaulHigin]

Disabling the new inline progress bar during inline debugging session seems reasonable to me.

[theJasonHelmick]

@ThomasNieto - Thank you for reporting this issue in the debugger.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.

Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.