Comment 5 for bug 289613

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

The cause of this was that we were listening to the wrong button element event. It's now fixed.