John Spackman

> @johnspackman I think we never had one single `keypress` event for `Ctrl+A` ... This belongs to `qx.ui.command.Command` Oh :( FWIW our own docs say in https://www.qooxdoo.org/5.0.1/pages/desktop/ui_interaction.html: > The keypress...

not as far as I know - but it would be great to have a PR before it gets lost in the midst of time :)

re: performance differences, i tend to agree - I imagine that it's performant enough that I've never worried about using [].join, and the more modern the browser the less there...

@stahl-riesa good point; qooxdoo next supports a slightly different set of features, but it uses a single closure method and no code generation at all https://github.com/qooxdoo/next/blob/master/framework/source/class/qx/Class.js#L506-L591

You're looking for the `myTable.stopEditing()` function

I agree, it should - you need to trap the "blur" event and then call stopEditing from there. If you want to make a PR that would be great 👍...

funny I thought I'd solved this in my apps but I've just tested one and it's not there! It would worth a quick test to see if a blur handler...

Originally we used `getObjectId()` and this broke existing code because it conflicted with existing developer code, so the "qx" prefix was a quick fix to work around that. But the...

yes, I think that was a mistake putting those `assertXxx` methods in there TBH, but nothing we can do about it now. However, I do think that it would help...

I'm curious to know why other editors don't have this problem, but OTOH the example that @rommni has given is pretty distilled down to showing that a contentEditable `div` is...