Rodrigo Girão Serrão
Rodrigo Girão Serrão
We should not prevent a message from being posted just because the state of the widget was changed programmatically, and even though the programmer already knows the state changed. E.g.,...
This tweaks the tokenizer to avoid parsing strings like "str1:str2" as rule declarations if `str2` is a valid pseudo-class and we're in a nested context. Fixed #4039. This PR depends...
Working on #3969 and #3999 we realised that pseudo-classes in nested selectors aren't correctly handled. (In short, to the tokenizer, a selector + pseudo-class looks the same as a rule...
See [this discussion](https://github.com/Textualize/textual/pull/3499#discussion_r1352573705) about the usage of `Decorator` versus `Decorator[..., ReturnType]` in `src/textual/_work_decorator.py`. EDIT: Last time I tackled this (and opened [PR #3862](https://github.com/Textualize/textual/pull/3862)) I ended up hitting what _looked_ like...
Adds support for the environment variable `TEXTUAL_ANIMATIONS`, which dictates which animations take place in Textual apps. (Kind of like a log level but for animations.) Fixes #3992.
Adds an `asyncio.Lock` to every widget. Fixes #4134.
`DOMNode.rich_style` does not take into account the text opacity when computing the foreground colour. This will _likely_ fix [Textual#3342](https://github.com/Textualize/textual/issues/3342), which in turn will _likely_ fix [Textual#3304](https://github.com/Textualize/textual/issues/3304).
(TL;DR: This is _likely_ the cause of [Textual#3304](https://github.com/Textualize/textual/issues/3304) and this will _likely_ be fixed if [Textual#3413](https://github.com/Textualize/textual/issues/3413) is fixed first.) Following #3304, an investigation showed that there are widgets for which...
As it stands, if you try to create a `SelectionList` with values that are not hashable, you get an error. That's because we use a dictionary to keep track of...