3 ms·
Wow, this comments thread is like a poster child for the unconstructive snark trend of HN. Anyway, I think it's a neat concept. It runs correctly for me in FF
by mistercow 14y ago
Wow, this comments thread is like a poster child for the unconstructive snark trend of HN.
Anyway, I think it's a neat concept. It runs correctly for me in FF (slow, but FF seems to be having problems taking advantage of my hardware in general for 3D stuff).
On Chrome and Midori it's fast, but the swinging effect gets clipped to the straight edges of the menus, and the text only shows up in the menu headings, rather than for the menu items themselves.
If I change the 'line-height' property for '.list dd' to 0, I can just make out the tops of the menu item ext, so I'm guessing that this is a positioning problem.
- zobzu 14y agolikewise, its painfully slow on ff even thus it renders correctly. i wonder what the cause is however. 3D stuff may go more or less fast on FF, but that one is particularly super slow.
- dmotz 14y agoUnfortunately Firefox still lags behind WebKit for CSS 3D transforms in performance and rendering quality (antialiasing). There's a fix for the latter issue, but it involves an even greater performance hit in my experience. I wrote another library that relies heavily on 3D transforms to do folding effects (http://oridomi.com http://oridomi.com) and it's frustrating seeing the same issues you see in Makisu in Firefox. Mozilla's been iterating quickly, so hopefully it's just a matter of time.
- mistercow 14y agoIn case anyone still reads this, I determined that the problem is that Chrome (and I guess Midori too) won't do any 3D CSS stuff via software rendering. I checked "Override software rendering list" in chrome://flags and it rendered beautifully and smoothly.