{"push_id":1729362621,"size":2,"distinct_size":1,"ref":"refs/heads/gh-pages","head":"aa70d4da2d44e15ad1a1bacc4a01276c005de186","before":"1eee7832d650542ff554032bb6c63059fbbff797","commits":[{"sha":"faad01852c8f843713d8de68e770fc46c1c6e1d8","author":{"name":"Aryeh Gregor","email":"b8dc250464a4b097490a906afadef0ee7cacb94e@aryeh.name"},"message":"Throw exception for removeRange on range that's not in selection\n\nThis matches Firefox, which was historically the only engine to ever\nhave a working implementation of removeRange.  WebKit still has none,\nEdge seems to be a no-op, and Chrome just added theirs in February.  If\nthere was only ever one implementation of the feature, the spec should\nfollow that implementation.\n\n(Firefox doesn't actually throw a DOMException here, it throws a\nnonstandard exception.  That's a side point, though.)","distinct":false,"url":"https://api.github.com/repos/w3c/selection-api/commits/faad01852c8f843713d8de68e770fc46c1c6e1d8"},{"sha":"aa70d4da2d44e15ad1a1bacc4a01276c005de186","author":{"name":"Ryosuke Niwa","email":"238d74b73e6abe2402cfe3f0b7534d1b8bfd0355@gmail.com"},"message":"Merge pull request #87 from w3c/removeRange-exception\n\nThrow exception for removeRange on range that's not in selection","distinct":true,"url":"https://api.github.com/repos/w3c/selection-api/commits/aa70d4da2d44e15ad1a1bacc4a01276c005de186"}]}
{"actor":{"display_login":"rniwa"}}