You can clone with
HTTPS or Subversion.
I'm using Chrome Canary (22.0.1215.1) for development and I released that wax and leaflet don't work together on this browser.
You can check documentation page (http://mapbox.com/wax/interaction-leaf.html) on Chrome Canary to see what's going on.
Can you see the problem in Chrome release cycle? This appears to work for me in Chrome Beta, and I'd rather not fix pre-release bugs in Chrome, of which there are many.
There is no problem with Chrome Beta (version 21.0.1180.49 beta)
I just want to inform you about the issue.
Thanks a lot.
Thanks, hopefully Google catches it before it lands :)
Unfortunatly not, Chrome Version 22.0.1229.79 (Win7) as well as latest stable version on Ubuntu has the problem from above. Any workaround?
Same thing in Chrome for mac. I'm currently using Chrome 22.0.1229.91 beta, but there are problems in the stable channel too.
the problem is with wax.offset, if you use $(el).offset return different values.
A quick fix (not tested in IE)
@ javisantana: Great, works without sideeffect in Chrome, Firefox, IE on Win7 (latest versions). Thanks for that!
@dooley thanks for testing.
also that fix solves some problems wax had with fixed positions on elements in the html page.
we have some testing for libraries that use wax, maybe is a good idea to "backport" them to wax to test this kind of things on different browser/OS/devices
@javisantana can you provide this as a pull request?
attemp to fix #242 (wax broken in chrome)
Pull request merged.
Fix worked for me, but it looks like the changes haven't made their way into dist/ on master. Thanks!
we have been using it extensively past months without any problem, i consider it fixed
Rebuilt and pushed in 1424765