{"push_id":1174093891,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"5599a52c899c1ed6fe331ec3884208af2cc667a8","before":"c1d478362a7f08d9d2031cfeaddcf63b68cb7885","commits":[{"sha":"5599a52c899c1ed6fe331ec3884208af2cc667a8","author":{"name":"Robert Knight","email":"d3a75f012596346a1e294e73943b7403ef1e26c3@gmail.com"},"message":"Fix the implementation of `isNodeInRange()` (#3522)\n\nThis function failed to account for the case where the node was\r\ncontained by, but not equal to, the range's startContainer.\r\n\r\nIn new browsers we could just use `Range.isPointInRange()`. Since that\r\nis not available in IE 10/11, add an implementation adapted from\r\nBlink's `Range::isPointInRange()` C++ impl, minus support for the\r\n`offset` parameter.\r\n\r\nThis fixes an issue where the adder could fail to show up when making\r\ncertain selections because `getTextBoundingBoxes()` could incorrectly\r\nfail to find the text nodes within certan ranges.\r\n\r\nFixes #3521","distinct":true,"url":"https://api.github.com/repos/hypothesis/h/commits/5599a52c899c1ed6fe331ec3884208af2cc667a8"}]}
{"actor":{"display_login":"nickstenning"}}