3 ms·
It appears to be Chrome only which might explain your problem with controls... Edit: Yes, I did only test in Firefox and Chrome. According to the comments belo
by philipbjorge 14y ago
It appears to be Chrome only which might explain your problem with controls...
Edit: Yes, I did only test in Firefox and Chrome. According to the comments below, it appears to work for modern browsers except Firefox.
- AdamTReineke 14y agoWorks in IE10. Why do you say Chrome only?
- donquix 14y agoMaybe he just tried Firefox and Chrome like me?
- gilgoomesh 14y agoWorks fine in Safari.
- thristian 14y agoMan, I can understand people writing Firefox-hating demos if they're trying to show off some feature that recently landed in WebKit, I can almost understand it if they just did a weekend-hack and couldn't be bothered testing in any browsers other than their own. I can't understand this - in 2013, how on earth do you break mouse events in JavaScript? We've had events like onmousedown working reliably across browser implementations for a decade or more, what on earth is going on?
- anglebracket 14y agoThe click handler is registered on the canvas and it checks e.offsetX. On Firefox, some people use e.layerX, but it's not exactly the same thing [0]. Someone posted a useful polyfill on JQuery's bugtracker [1]. Firefox should just support offsetX as well, but they don't, for whatever reason. [0] https://bugzilla.mozilla.org/show_bug.cgi?id=122665#c3 https://bugzilla.mozilla.org/show_bug.cgi?id=122665#c3 [1] http://bugs.jquery.com/ticket/8523#comment:16 http://bugs.jquery.com/ticket/8523#comment:16