We can have hover effects on squares, something like this.
Some people might find it a bit distracting, so I'm not sure we really want to pursue this.
But the problem is that at the edge, between individual squares, chrome is not being consistent:
This is the reason why we use hover class and not :hover for destinations.
Easy solution would be to use elementFromPoint to get the current square. But I'm a bit worried about performance in processDrag, since it would get called in each raf (https://gist.github.com/paulirish/5d52fb081b3570c81e3a).
Another solution would be to update hover class of each square on mouseMove event, but that might also not be optimal.
We can have hover effects on squares, something like this.
Some people might find it a bit distracting, so I'm not sure we really want to pursue this. But the problem is that at the edge, between individual squares, chrome is not being consistent:
508 is smaller than 508.78125, therefore this is not the element we should get. Works correctly in firefox.
This is the reason why we use hover class and not :hover for destinations.
Easy solution would be to use
elementFromPointto get the current square. But I'm a bit worried about performance in processDrag, since it would get called in each raf (https://gist.github.com/paulirish/5d52fb081b3570c81e3a). Another solution would be to update hover class of each square on mouseMove event, but that might also not be optimal.