Tom MacWright

I'm confused: are you trying to document JavaScript? If you'd like to turn off inference, there's a [troubleshooting topic for that](https://github.com/documentationjs/documentation/blob/master/docs/TROUBLESHOOTING.md#documentation-is-inferring-too-much-about-my-code) - the gist is to use the name tag...

Can you try using `@name test` to avoid inference in this case?

You can use the `@memberof` tag to add the tree structuring. Right now that's basically how this works: you can have inference, or you can turn it off, for a...

Are you using CommonJS or es6 imports? Can you share a link to the source code, or any other details?

@pixelfreak - I'll be working on this area and addressing this in the #84 ticket. If you want to de-convolute the code, go for it.

@pixelfreak try the `ff` branch: it defers tile loading and changes the CSS transforms strategy. Currently at the cost of Firefox & IE compatibility, but that should be fixable soon.

I don't think so, unlike the purpose of the rest of the callbacks, layer changes are always started by user code, so the developer will always know & be able...

Nope - at least it's not planned at this point. We're trying to keep legacy browser support here, and there's no way to rotate a canvas or individual images in...

It's worth a shot; if you want to go for it, try it out. There'd probably be one stage of just supporting rotation on the element, and then another of...

Hmm, any browser in particular you're seeing this on? The example looks pretty smooth to me.