Darren Burns

@DrBenton There is an open PR above for this ^ Although I thought this wasn't an issue on the `css` branch

Moving focus to something off-screen will cause the browser window to scroll such that the newly focused element is visible, for example.

It feels like we would want to write the final "frame" of the progress bar rather than excluding it entirely?

I can't reproduce this. Running the same Python version, Rich version, tried legacy/non-legacy terminals, tried forcing the encoding to cp1252 and utf-8, tried with an without running in a subprocess....

It was an issue with rendering on "legacy" terminals on Windows, so would only affect people using older versions of cmd. In legacy rendering, Rich calls Win32 APIs directly, rather...

Added in https://github.com/Textualize/rich/pull/2470, so should be fixed in the next release. Let us know if not.

Hi @philiparvidsson, thanks for the report. I'd just like to confirm a few things: * After you import the module, does anything happen at all? Did the "live display" not...

I think #2172 is unrelated to what actually gets written to the terminal and is instead about `record=True` not recording things that occur inside a `Capture` context. Doesn't impact developing...

@nathanrpage97 I agree, I don't think `echo` is the right term either 🤷‍♂️ `tee` has better semantics to me but I had to click the link you provided as I...

Hey @tylerflex, I haven't been able to reproduce this. Are you running this in VS Code, the Jupyter Notebook web interface, or somewhere else? I noticed in the diagnostics you...