"It does this by detecting whether the start of the selection is a mutable entity, and if it's not, falling back to the backspace method normally used as part of the keyDown event handler."
I'd like to understand that part of the change more.
It's true that in android, when the user hits 'delete', that triggers the 'editOnInput' callback, and in that case we could just call the 'keyCommandPlainBackspace' method.

• What about the other cases where 'editOnInput' gets called? It gets used for a bunch of things. Maybe we should split it into some separate handlers - it's getting convoluted I think.
• Why would we not call 'keyCommandPlainBackspace' when there is a mutable entity present?

So some ideas from our meeting:

• It seems like the core issue is that Draft tries to listen to keyDown and it's not there on delete in Android with that keyboard. We could file a bug and/or file a bug and push to have it fixed.
• we could try to write unit tests around this; that might make the issues more clear and help us find other changes that will fix the problem
  • for inspiration look at the DOM selection unit tests
• let's be careful and understand this behavior before merging this or any similar change
• let's be intentional about which conditional blocks we gate to Android; that might warrant more discussion
  • we might look at the way we handle 'cut' where we let the DOM get mutated and then force a re-render to get it back into a good state

Hope that is helpful, and sorry that we're not prepared to merge this change.

Since we never resolved the questions and problems with this PR, and nobody is currently working on fixing the known issues with Android web, I'm closing this.