TinyMCE per block: Trying the temporary content editable approach for cross-block selection

[youknowriad]

For now, it supports:

• Cross selection using the mouse
• Deleting the selected content

I noticed this introduced a bug when selecting inside a TinyMCE (the cursor jumps)

[ellatrix]

This seems to be a PR where we start to reimplement a lot of behaviour that we'd normally have with a single content editable field. I'm not sure if it's a good idea to temporary set a global content editable attribute instead of just having it there permanently, but limiting inter-block behaviour where we want it.

What's the benefit of introducing rangy?

[youknowriad]

@iseulde This was a PR to play with multiselection in the multi-prototype instance (as a POC). It's not intended to be merged.

I'm not sure if it's a good idea to temporary set a global content editable attribute instead of just having it there permanently, but limiting inter-block behaviour where we want it.

I don't have strong opinions, I tried both approach and this is was the most promising one I could come up with at that moment.

rangy?

This was introduced to ease the manipulation of the Selection and ranges. I found it easier to work with instead of the different browser implementations of the Selection API.

[youknowriad]

I'm closing this for now

[ellatrix]

@youknowriad So what do you see as a way to enable inter block selection? Or is the way forward a shared block?

[youknowriad]

@iseulde I think the approach in this PR is possible but I'd use your proposal to limit inter block selection to the whole blocks instead of trying to figure out which part of the blocks were selected.