Not necessarily an important bug, but I noticed that on a squirt-readable page clicking the squirt button multiple times will cause squirt to queue multiple read-throughs of the desired text. While there are multiple read-throughs queued each read-through is executed as if squirt must finish all the queues in the time normally allotted for one read-through (e.g. clicking 4 times turns 350 WPM for one read-through to 1400 WPM for 4 read-throughs; each taking 1 minute to complete their tasks on a 350 word page). This is not really an issue unless you're using the squirt button like a madman/idiot, but I'm sure this queuing issue is undesired behavior for squirt.
Correction: Appending my previous issue above, this speeding up only seems to occur after one zooms in ('ctrl' + '+') then zooms out ('ctrl' + '-'). Upon zooming out after zooming in, the speeding up kicks in.
Not necessarily an important bug, but I noticed that on a squirt-readable page clicking the squirt button multiple times will cause squirt to queue multiple read-throughs of the desired text. While there are multiple read-throughs queued each read-through is executed as if squirt must finish all the queues in the time normally allotted for one read-through (e.g. clicking 4 times turns 350 WPM for one read-through to 1400 WPM for 4 read-throughs; each taking 1 minute to complete their tasks on a 350 word page). This is not really an issue unless you're using the squirt button like a madman/idiot, but I'm sure this queuing issue is undesired behavior for squirt.