Bob Ippolito

I think most of these tests failures probably just mean that you have to change the tests to expect the tabNode class, but they need to be fixed nonetheless.

There is ongoing work to make most of the functionality that ships with Lexical framework independent, but in the meantime there third party projects to make Lexical easy to use...

I don't think that nested tables are currently well supported, I'm sure there are a number of related edge cases. If you are interested in this feature I suggest that...

This should have been fixed by #6889

As a new contributor, for security reasons, GitHub doesn't automatically run the CI tests before a reviewer clicks a button. It'll probably fail when they are run.

I think in this scenario you also need to consider cases where anchor.offset !== focus.offset, we know that anchor.offset === 0 but we don't know what focus.offset is, so it...

I think the first step would be to follow @GermanJablo's suggestion and make the removeText unconditional, without going deep into the code and seeing which tests that affects it would...

Closing as this PR is stale and incomplete

It's not supported to have DOM nodes in the editor that are unmanaged by Lexical except in a DecoratorNode. If this feature were to be considered it would need tests...

Your code is not formatted correctly so I can't read it, but you probably have multiple versions of lexical installed. All installed lexical and @lexical/* packages must be the exact...