Cursor shape: Filled box does not work as expected.

[kgfly]

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.1413

Other Software

No response

Steps to reproduce

Change cursor shape to Filled box
type aaa
and move back one character.

Expected Behavior

Windows classic console

You can see "a" easily, under the cursor. The black font is easy to see.

Linux has similar behavior.

Actual Behavior

It's hard to see "a" under the cursor. The gray font is hard to see.

[lhecker]

As a workaround, until we fix the default text renderer, you can opt into the upcoming text renderer here:

After clicking save, you have to close and reopen all your tabs.

[kgfly]

Thanks.

Is there an active tracking item for "until we fix the default text renderer, "?

[YUSHACOD]

The thing with the current work-around is that it will work for certain color schemes but not so well for others. This is very annoying as the cursor is the most important part of the terminal app. And working without being able to see the text is an horrible nightmare.

[lhecker]

If you don't mind, could you give me an example for a color theme with which the workaround doesn't work? I'd be interested in fixing any such issues.

---

Is there an active tracking item for "until we fix the default text renderer, "?

Edit: No there isn't. Let's use this one. 🙂

[lhecker]

Oh, I think I can already guess what the issue is. Some themes use colored cursors and if the theme specifies colored cursors, we do draw them in that exact color. This affects all 3 built-in light themes.
Right now, it's a bit of a hidden trick, but to get inverted cursors in AtlasEngine you have to make sure the cursor color is set to #FFFFFF. I think once we roll that new text renderer out as the default, there's a high chance we'll modify all built-in themes to use such inverted cursors instead of colored ones.

[YUSHACOD]

Oh, I can't thank you enough. It works perfectly now. Just setting the cursorColor did the trick.

[zadjii-msft]

I'm gonna call this a /dupe of #9610, yea? basically, there is an undocumented way to get cursor inverting, but we still need to spec up the right way to definitely support it.

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!