Thanks for the report, I can reproduce this as well (macOS/Chrome 64)
The bug is caused by
onKeyDown = (event, change) => {
const { value } = change
const { document, selection } = value
const { startKey } = selection
const startNode = document.getDescendant(startKey)
if (selection.isAtStartOf(startNode)) {
const previous = document.getPreviousText(startNode.key)
const prevBlock = document.getClosestBlock(previous.key)
if (prevBlock.type == 'table-cell') {
event.preventDefault()
return true
}
}
Where
if (prevBlock.type == 'table-cell') {
event.preventDefault()
return true
}
disable the text insert;
I think we shall only disable delete operations; or at least pass the insert operations
Yeah I agree, that seems to be correct. Looks like it's only a problem with the example implementation and not with slate itself. @zhujinxuan want to send a PR fixing that?
@schneidmaster Yes, give me some minutes~
A bug happens when insert at start:
Strangely, the text is bolded

Hmm, looks like it's carrying over the bold mark from the previous cell? (Maybe due to #1561)
Let us fix it after https://github.com/ianstormtaylor/slate/issues/1561
I think perhaps there is a bug of carrying mark in selection normalization.
We can fix that after https://github.com/ianstormtaylor/slate/pull/1645
Any updates regarding this bug?
@amitm02 Oh, I forgot that. I will submit a PR in this week.
Most helpful comment
Let us fix it after https://github.com/ianstormtaylor/slate/issues/1561
I think perhaps there is a bug of carrying mark in selection normalization.