aboutsummaryrefslogtreecommitdiff
path: root/ext/fg/js/document.js
Commit message (Collapse)AuthorAge
* reimplement ignored chars inside source.js onlysiikamiika2019-08-15
|
* ignore zero-width non-joinersiikamiika2019-08-14
| | | | fixes #179
* fix scanning start of line on Firefoxsiikamiika2019-08-04
| | | | | | | | | | | | On many sites, for example Twitter (posts), Yomichan doesn't match any text from the beginning of the line unless you move the mouse cursor to the top left corner of the word that starts from the beginning of the line. Apparently there were some problems related to the imposter and there was commit 0cc5566 adding a fix for it, but this seemed to cause problems and 542cdb2 was added to fix that. It didn't handle all of the cases, though, so this commit is letting everything through on Firefox.
* Fix docRangeFromPoint sometimes not returning resultstoasted-nutbread2019-06-22
| | | | If range.getClientRects() has more than 1 result, it is possible that nothing will be returned even when hovering over a valid target.
* Improve handling of null values from caretRangeFromPointtoasted-nutbread2019-02-20
|
* Catch exceptions thrown by range.getClientRects()toasted-nutbread2018-12-10
| | | | Firefox dev 65 was throwing an exception
* Fixes for imposter element and range y positionGareth Parker2018-06-08
| | | Hides the imposter element once we've finished using it and checks the y position for the range against the point given
* Place `nodeType` checks inside `caretRangeFromPoint` functionRoderic Day2017-10-13
| | | | | Checked that it does not un-fix #80 Squelches alerts (but does not fix underlying issue) for #89
* make sure ranges are created over text nodes only (fixes #80)Alex Yatskov2017-09-19
|
* bugfix and versionAlex Yatskov2017-08-19
|
* fix flicker on form elements on mouseover (fixes #56)Alex Yatskov2017-08-17
|
* cleanupAlex Yatskov2017-08-14
|
* cleanupAlex Yatskov2017-07-20