Feature (Epic?): Improve Panzoom for nested content use case (list of components, etc.) about panzoom

[timmywil]

Thanks for your incredibly well articulated feature request! There are a lot of good suggestions here. Making Panzoom smarter, especially in the case of canvas is something I've always wanted to do, but when I've tried it in the past, the resulting code is much larger than I'm comfortable with. Panzoom is meant to be small, but the trade off is that it is low-level and not always smart in every case. I think it's great for what I consider to be the most common cases.

That said, the time you've put into this ticket alone is a strong argument for reconsidering my position. This may be a good time for a rewrite, especially considering Panzoom was originally built with support for IE (which, by the way, is why I couldn't change transform-origin to 0 0). It literally won't let you for certain elements.

I'm going to leave this open and add votes needed. Normally, I would close it to add it to the feature votes pipeline, but I'm willing to bet there will be more tickets open that I could close as dupes of this one.

[nwittwer]

Thanks for the consideration and sharing your thoughts, @timmywil!

That sounds like a great direction. Would be really cool to see what an even better, smarter, modern (non-IE) version of Panzoom would look like!