- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 01 Aug 2016 12:57:33 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Monday, 1 August 2016 20:00:51 UTC
Another option would be to enable the data attribute of the beforeinput event for such cases. So it could carry information about what character(s) to add in replacement of what is in the first targetRange. But again, if there is no browser that currently handles this type of editing of text with ligatures in a special way, and additionally usage of ligatures in source text creates issues for moving the caret, this may not be all that important right now. What do you think @garykac ? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/133#issuecomment-236689205
Received on Monday, 1 August 2016 20:00:51 UTC