Skip to content

Region invalidation malfunctioning after text buffer has begun to scroll #11214

Closed

Description

@oising

Windows Terminal version (or Windows build number)

1.11.2421.0

Other Software

  • Windows 11 / 21H2 / 22000.132

Steps to reproduce

  • open powershell (could be another shell)
  • execute "ls" / "dir" a few times until the text buffer has begun to scroll

Parts (or the entirety) of the buffer should be invisible, yet will be rendered visible if selected with the mouse

e.g.
image

after selection:
image

Expected Behavior

  • text rendered correctly 💩

Actual Behavior

  • text rendered incorrectly

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Sep 13, 2021
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Sep 13, 2021
  3. added
    Area-RenderingText rendering, emoji, complex glyph & font-fallback issues
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    and removed
    Needs-Tag-FixDoesn't match tag requirements
    on Sep 13, 2021
  4. jessey-git commented on Sep 13, 2021

    @jessey-git

    I've also been seeing this since moving to 1.11 preview (usually with various git commands for me). I didn't notice at all in the 1.10 preview so perhaps a regression.

  5. 15 remaining items

  6. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Mar 1, 2022
  7. guhetier commented on Mar 14, 2022

    @guhetier

    I could reproduce this consistently by:

    • opening a terminal on one screen
    • running ls
    • moving it to another screen with a different resolution
    • running ls
  8. zadjii-msft commented on Apr 8, 2022

    @zadjii-msft
    Member

    I'm really hoping this was fixed as a side-effect of #12713 (but that hasn't yet been pushed out in a servicing build yet).

  9. oising commented on Apr 8, 2022

    @oising
    CollaboratorAuthor

    I'm really hoping this was fixed as a side-effect of #12713 (but that hasn't yet been pushed out in a servicing build yet).

    From my perspective on how it manifests, that looks hopeful for sure.

  10. zadjii-msft commented on Aug 15, 2023

    @zadjii-msft
    Member

    Hey Oisin Grehan (@oising) you still seeing this, like maybe on 1.18/? We've re-written the renderer a couple times since this was filed, I'm thinking this might have gone away on its own 😅

  11. oising commented on Aug 15, 2023

    @oising
    CollaboratorAuthor

    Mike Griese (@zadjii-msft) Hey Mike! Nope, haven't seen this in a long time. I've got redraw off, s/w off and using the new renderer. I guess close it?

  12. added
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    and removed
    Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to something
    on Aug 15, 2023
  13. oising commented on Aug 15, 2023

    @oising
    CollaboratorAuthor

    Closed as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-RenderingText rendering, emoji, complex glyph & font-fallback issuesHelp WantedWe encourage anyone to jump in on these.Issue-BugIt either shouldn't be doing this or needs an investigation.Needs-AttentionThe core contributors need to come back around and look at this ASAP.Needs-ReproWe can't figure out how to make this happen. Please help find a simplified repro.Needs-Tag-FixDoesn't match tag requirementsPriority-3A description (P3)Product-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions