- From: Kelly Miller <lightsolphoenix@gmail.com>
- Date: Wed, 10 May 2006 02:43:42 -0400
- To: Emrah BASKAYA <emrahbaskaya@hesido.com>
- CC: "www-style.w3.org" <www-style@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Emrah BASKAYA wrote: | | The things mentioned in this thread for transition effects are very | strictly a scripting job. Drawing a line between basic required | behaviour for accessibility (:hover), and eye-candy effects (opacity | fade on hover) is actually very easy. While we are discussing presentation/behavioural stuff and accessibility, I'd like to bring up a problem I ran into when trying to do CSS menus that were accessible. Simply put, :focus does not work like :hover, forcing the use of Javascript to define behaviour most likely to be used by those who need the accessibility, and who will likely have Javascript turned off... which defeats the point of using it at all. I think CSS needs a way of detecting states, both on objects and on descendants of objects. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEYYubvCLXx0V8XHQRAsxoAJ95Ox1aPSuEFLuFTGaEV8RVP5VhygCbBz1C 6vkSRaRlRbQZGdb2BgsjjgE= =YQVU -----END PGP SIGNATURE-----
Received on Wednesday, 10 May 2006 04:54:47 UTC