- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 22 Mar 2017 22:55:47 -0700
- To: w3c/selection-api <selection-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 March 2017 05:56:43 UTC
It seems this will also be useful for doing measurements, for example to create beforeinput events in JavaScript. The only odd aspect to it there is that one needs to be OK with losing the selection temporarily in order to do the measurement [1], but I guess that's not a major cause for concern? Is there any reason why this is part of selections rather than ranges? If one could extend ranges like this, one could use it both for selection and for measurement purposes without losing the selection. [1] https://github.com/w3c/input-events/issues/54 -- 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/selection-api/issues/37#issuecomment-288624547
Received on Thursday, 23 March 2017 05:56:43 UTC