| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Only return unique elements from docElementsFromPoint | toasted-nutbread | 2019-12-17 |
| | | | | | This fixes #294 | ||
| * | Remove unnecessary escapes from regex literals | toasted-nutbread | 2019-11-26 |
| | | |||
| * | Create DOM utility file | toasted-nutbread | 2019-11-26 |
| | | |||
| * | Fix incorrect opacity check | toasted-nutbread | 2019-11-25 |
| | | |||
| * | Add correction to offset of imposter rect | toasted-nutbread | 2019-10-17 |
| | | | | | Necessary when dealing with CSS transforms | ||
| * | Handle null return value of document.caretPositionFromPoint | toasted-nutbread | 2019-09-18 |
| | | |||
| * | Normalize XHTML document node.nodeNode to upper case | toasted-nutbread | 2019-09-15 |
| | | |||
| * | Return only single element when deepDomScan is not enabled | toasted-nutbread | 2019-09-14 |
| | | |||
| * | Remove destructuring from searchAt, containsPoint, docRangeFromPoint | toasted-nutbread | 2019-09-14 |
| | | |||
| * | Replace some instances of Array.concat | toasted-nutbread | 2019-09-02 |
| | | | | | .push or .unshift can accomplish the same operation without constructing new arrays. | ||
| * | Fix typo | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Fix issues caused by scanning ranges which don't start with a text node | toasted-nutbread | 2019-09-02 |
| | | | | | The rects returned by range.getClientRects() could include the entire start element's bounding box. | ||
| * | Fix issue with whitespace ranges | toasted-nutbread | 2019-09-02 |
| | | | | | The size of the rects for these ranges will sometimes be excessively large on Firefox, leading to false positives. | ||
| * | Reduce amount of isPointInRange calls for repeated ranges | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Add option for enabling deep scanning | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Allow elements behind other transparent elements to be scanned | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Improve definition of caretRangeFromPoint | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Destructure point to {x, y} only once | toasted-nutbread | 2019-09-02 |
| | | |||
| * | Create container for imposter element | toasted-nutbread | 2019-09-01 |
| | | | | | The container will prevent the imposter element's size from affecting the document's primary scrollbars. | ||
| * | Use important CSS priority for imposter element styles | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Fix imposter issues with <input type="text"> | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Make the imposter element tracked using TextSourceRange | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Disable pointer events on hidden imposter | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Remove rounding | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Fix some size and positioning issues related to imposter element | toasted-nutbread | 2019-08-31 |
| | | |||
| * | Update isPointInRange to be more accurate | toasted-nutbread | 2019-08-29 |
| | | |||
| * | Clean up docRangeFromPoint | toasted-nutbread | 2019-08-16 |
| | | | | | | | Use a cached value for checking if the browser is Firefox. Only validate and set up document.caretRangeFromPoint once. Use switch for multiple comparisons on the same value. | ||
| * | fix scanning start of line on Firefox | siikamiika | 2019-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 results | toasted-nutbread | 2019-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 caretRangeFromPoint | toasted-nutbread | 2019-02-20 |
| | | |||
| * | Catch exceptions thrown by range.getClientRects() | toasted-nutbread | 2018-12-10 |
| | | | | | Firefox dev 65 was throwing an exception | ||
| * | Fixes for imposter element and range y position | Gareth Parker | 2018-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` function | Roderic Day | 2017-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 Yatskov | 2017-09-19 |
| | | |||
| * | bugfix and version | Alex Yatskov | 2017-08-19 |
| | | |||
| * | fix flicker on form elements on mouseover (fixes #56) | Alex Yatskov | 2017-08-17 |
| | | |||
| * | cleanup | Alex Yatskov | 2017-08-14 |
| | | |||
| * | cleanup | Alex Yatskov | 2017-07-20 |