IE9 doesn't support it, so just ignore it instead of throwing an error.
This fixes a bug with Opera where the map size was empty.
Wheel events are utterly broken. Even though WebKit's mousewheel precision bug has been fixed, Chrome and Safari still differ in terms of mousewheel acceleration. Safari and Firefox report the correct value (the number of pixels that would be scrolled), but Chrome does not. I've not tested Opera or IE9. Fortunately, we can determine exactly the number of pixels that would be scrolled by dispatching the mousewheel event to a scrollable area, and then observing the change in scrollTop. However, dispatching the received event is not strictly allowed, so ignore this error and hope for the best.
Thanks to @natevw, I see there are `scale` and `rotation` fields on the touch event that we can use to compute the zoom and angle offsets more easily. Also, this commit updates the example to auto-detect retina displays using the devicePixelRatio field of the current window.
This adds basic touch support, including single touch (pan) and double touch (pan and zoom). In a future change, I'd also like to support rotation for double touch, and double-tap to snap to the nearest integer zoom level. This commit also includes a simple example that shows how to specify 2x resolution tiles for the iPhone 4's retina display.
Conflicts: polymaps.js polymaps.min.js src/start.js
Rename `parse` -> `parser`, `format` -> `formatter`. Parser now calls `map` setters instead of returning an array.
For example, if a non-array is returned by `parse`.
These can be used to override the default location hash formatting e.g. to add other parameters. As `parse` is called every time the location hash changes, it can be used to detect other parameters at the same time.
Instead of setting the image URL to `about:blank`, no image URL is set when `null` URLs are detected. This appears to be slightly faster than using `about:blank`, at least in Firefox. I've updated `po.image`'s `repeat` accordingly.
True by default. Can be set to false to disable column wrap-around.
This content has been moved to the gh-pages branch.