DotDragnet
May 24, 2012, 07:08:56 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: follow us on twitter @dotdragnet
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: mouseover not firing in 3D transform list  (Read 270 times)
samhs
Administrator
Hero Member
*****
Posts: 1713



View Profile WWW Awards
« on: September 12, 2011, 08:31:49 AM »

I'm prototyping an effect using 3D transformations and transitions (so it will only work properly in webkit based browsers). That's all working fine - better in Safari than in Chrome - but fine.

However, something I did when making sure that Chrome stacked up the Z-index properly has stopped my mouseover events firing properly - the image below should explain:



http://www.hs-demo.co.uk/coverflow/

Any idea why it's not firing? I've tried removing the z-index stacking and the negative margins - but it's still not having it. It's not a performance issue as can be seen by using the keyboard to navigate - so I'm confused. Thoughts?

TIA
Logged

Loose adj a not held together; not fastened or firmly fixed in place
Lose verb to misplace something. To fail to keep or obtain something, especially because of a mistake, carelessness, etc.
---
Blog: www.ohwrite.co.uk
Twitter: www.twitter.com/samhs
samhs
Administrator
Hero Member
*****
Posts: 1713



View Profile WWW Awards
« Reply #1 on: September 12, 2011, 08:34:05 AM »

I should have also said - the only reason I've got that z-index routine at the bottom of each function is that Chrome was stacking up the cards after the active one incorrectly. It was right in terms of stack, but wrong in terms of how they should overlap in 3D space - it seems to render in 2.5D rather than true 3D.

*and*

It does fire if you move off the side of the area shown, but feels very clunky - before I started messing around for Chrome it was arguably the other way - too responsive, but I can't see what I've done to fubar it.
« Last Edit: September 12, 2011, 08:38:29 AM by samhs » Logged

Loose adj a not held together; not fastened or firmly fixed in place
Lose verb to misplace something. To fail to keep or obtain something, especially because of a mistake, carelessness, etc.
---
Blog: www.ohwrite.co.uk
Twitter: www.twitter.com/samhs
samhs
Administrator
Hero Member
*****
Posts: 1713



View Profile WWW Awards
« Reply #2 on: September 12, 2011, 06:49:21 PM »

Okay, I've admitted defeat and worked around the problem instead by testing for mouse movement within the overall <div>, checking to see if it's to the left or right of the main currently-selected object, and clicking down or up one in the stack as appropriate. That made it very very very responsive - far too responsive in fact, so I had to add in a little sampling-speed code so that it will only make one update per second, but it seems to be working nicely now.

Would still be interested to hear if anyone has insight into why mouseover wasn't firing properly though.
Logged

Loose adj a not held together; not fastened or firmly fixed in place
Lose verb to misplace something. To fail to keep or obtain something, especially because of a mistake, carelessness, etc.
---
Blog: www.ohwrite.co.uk
Twitter: www.twitter.com/samhs
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2006-2008, Simple Machines Valid XHTML 1.0! Valid CSS!