Bob Ippolito

You can change this behavior in your own editor by setting `aria-relevant="all"` or `aria-relevant="additions removals text"` on the contentEditable element. The browser default is `"additions text"` which is why removals...

Well in this case I tried it by adding only the aria-relevant attribute to the contentEditable and it had the behavior of announcing deletions in addition to input. I don't...

It seems you're right, I must've accidentally switched over to Chrome which does seem to do the expected thing either way

I think this might just be a Safari or WebKit bug, it's unclear if we could do anything about it. Even if I change the code to use the semantic...

For what it's worth the methods that Lexical currently uses for updating a TextNode are to replace the `domTextNode.nodeValue = newText`, or if it's firefox or in composition mode it...

I couldn’t tell you why the code is there, I just moved it from somewhere else because it seemed less likely to cause test failures in that spot. You’d have...

I would guess that this has to do with the implementation of `$unwrapArtificialNodes`

It really depends on what you mean by support. Does lexical have code that imports tables from html? Yes. Does it work in every possible scenario? No. It's a complicated...

I can't reproduce this

@citruscai I think it could be worth making an example, maybe another kind of node + plugin in the playground or a standalone example. I think the `useLexicalTextEntity` facility would...