Bob Ippolito

I think the best solution to this is probably something else. If it was merely a decorator node selection issue then the issue wouldn't be platform specific. It seems more...

There multiple scenarios where the lexical selection doesn't match the browser's selection by design, otherwise the SelectionAlwaysOnDisplay plug-in would have no purpose. I'm sure that some coherent solution exists but...

The screenshots aren’t very useful, the important details are what the browser selection and lexical selection are (plus the events themselves). The issue must be something to do with the...

Looking a little deeper the paste issue seems specifically to be that Firefox ends up dispatching another event when processing the paste that Lexical dispatches as a CONTROLLED_TEXT_INSERTION_COMMAND which doesn't...

Did you try changing `type` to `interface` first? It's not as complete of a solution but TypeScript is generally a lot better at reporting mistakes when you are using `interface`...

does it give you an error if you specify it as a literal inline in the jsx, or if you provide an explicit type annotation for the variable?

Closing this PR due to staleness! If there are new updates, please reopen the PR.

@birtles if you take a look at https://github.com/facebook/lexical/pull/7317 I think all of these issues are sorted in a way where you can delete your workarounds for delete and arrow keys,...

Great, I’ll look a bit deeper. Didn’t do any WebKit testing or look at any of the e2e failures, but since you confirmed that this approach sorts out your navigation...

I'd need to know exactly what the corresponding lexical document looks like, the HTML is only half the story. With regard to controlling the cursor location a better solution than...