jaukia / zoomooz

An easy-to-use jQuery plugin for making zooming web pages.
http://janne.aukia.com/zoomooz/
1.79k stars 275 forks source link

Every child element (unintentionally) serves as click-to-zoom-out #81

Closed perdittmann closed 11 years ago

perdittmann commented 11 years ago

Hi everyone,

I just started using zoomooz today, and I am really excited about it. Thanks for the good work.

There is one thing, though, that I am stuck on that confuses me. My idea is to have for screens on one main screen. You click on one, it gets zoomed in. On the enlarged screen, you have a button that gets you back to the first screen with all four of them.

I encounter something strange: The way I chose does not seem to work, my button does nothing. But when I add a stray

<div class="zoomTarget"></div> 

(that has no content) before my code, every child element of my target screen serves as click-to-zoom-out – which is not what I intended, of course.

You can see my code here: http://jsfiddle.net/zxYjr/

Have you any idea what triggers that click-to-zoom-out thing? What would be the right syntax for the script in the button?

I am not trying to get you to do my work here – I spent most of today trying to figure it out myself. I hope I am just missing something very obvious and maybe someone can point me in the right direction, so I can continue myself.

Many thanks in advance! Per Hamburg, Germany

jaukia commented 11 years ago

I'll try to have a look at this at some point, thanks for the example!

jaukia commented 11 years ago

All of your zoomTargets ought to be inside a zoomContainer. Otherwise they will not control the zooming of the viewport element, but instead, probably zoom the body of the image, or something. So that is not what you want to do.

Currently, to make the back buttons, you have to use javascript. There is a story on easier making of back buttons, but that one is not yet implemented: #44

To fix your issue, just delete the empty zoomTarget. Let me know if this opens up further issues, but it should solve the problem currently described in this issue, so I'll close the story.