Bob Ippolito
Bob Ippolito
Yes, of course you can catch the keyboard event and handle it yourself, or add a listener for the DELETE_CHARACTER_COMMAND and handle that yourself.
See also #4040 #1968
In this particular case the reason the images are there are for input reasons rather than rendering reasons. I think your testing approach is correct, but it sounds like you...
This PR doesn't have a signed CLA and the review comments have not been addressed
Are all of the statics valid in free threading? I haven’t read through the required changes but I would imagine it’d be better to have per-interpreter references rather than process...
I think for iteration all that's needed is to essentially copy that macro? AFAICT _PyCriticalSection_Begin is just the static inline internal version of PyCriticalSection_BeginMutex. https://github.com/python/cpython/blob/main/Include/internal/pycore_critical_section.h#L29-L42
It looks like it was backported to 3.14 according to that issue?
https://github.com/python/cpython/blob/v3.14.0/Include/cpython/critical_section.h#L76-L77
Still valid in v0.21.0. I think this is basically another presentation of #6086 - the selection anchor or focus always migrates to the TextNode during normalization and our delete code...
@zurfyx is there a reason why this selection color is hard-coded as a style, rather than implemented as a class and/or using css custom properties?