toasted-nutbread
|
542cdb2df9
|
Fix docRangeFromPoint sometimes not returning results
If range.getClientRects() has more than 1 result, it is possible that nothing will be returned even when hovering over a valid target.
|
2019-06-22 21:42:35 -04:00 |
|
toasted-nutbread
|
dd52a1c01a
|
Improve handling of null values from caretRangeFromPoint
|
2019-02-20 21:47:31 -05:00 |
|
toasted-nutbread
|
33ec369eff
|
Catch exceptions thrown by range.getClientRects()
Firefox dev 65 was throwing an exception
|
2018-12-10 17:09:06 -05:00 |
|
Gareth Parker
|
0cc5566886
|
Fixes for imposter element and range y position
Hides the imposter element once we've finished using it and checks the y position for the range against the point given
|
2018-06-08 22:48:26 +01:00 |
|
Roderic Day
|
5502bf8aed
|
Place nodeType checks inside caretRangeFromPoint function
Checked that it does not un-fix #80
Squelches alerts (but does not fix underlying issue) for #89
|
2017-10-13 15:12:41 -04:00 |
|
|
|
0554aa0d27
|
make sure ranges are created over text nodes only (fixes #80)
|
2017-09-19 23:05:17 -07:00 |
|
|
|
c4525027da
|
bugfix and version
|
2017-08-19 21:09:54 -07:00 |
|
|
|
191336522c
|
fix flicker on form elements on mouseover (fixes #56)
|
2017-08-17 19:14:06 -07:00 |
|
|
|
211e5d1155
|
cleanup
|
2017-08-14 23:22:37 -07:00 |
|
|
|
8bcc4ddf19
|
cleanup
|
2017-07-20 21:21:22 -07:00 |
|
