- From: Tantek Çelik <tantek@cs.stanford.edu>
- Date: Thu, 20 Feb 2003 16:23:16 -0800
- To: Chris Vincent <dris86@cox.net>, <www-style@w3.org>
On 2/20/03 3:50 PM, "Chris Vincent" <dris86@cox.net> wrote: > Heh, I feel a bit dumb now. Don't. That was not the intent. > I figured :active was just for links. It _was_ defined that way in CSS1. And so CSS1 UAs (like IE6/Windows and IE5/Mac) only support :active on links. CSS2 broadened :active to apply to all elements. http://w3.org/TR/CSS2 There are no CSS2 UAs (if there are, Chris Wilson owes a lot of beer[1]), but there are many UAs that support portions of CSS2. At this point no one really expects a complete CSS2 UA to ever be developed. A complete CSS2.1 UA is much more likely. http://w3.org/TR/CSS21 > Working with browsers that don't support CSS properly has messed up my > perspective. LoL. Hmmm... I wonder what that says about me. Or any other browser developer. Since most of what we do with work <del>with</del><ins>on</ins> such browsers. > I was thinking though, would it be possible to > apply the same sort of things to keyboard events? Perhaps. Something like :key-active(c) ? Note that there is the 'key-equivalent' property in CSS3 UI which enables some styling of keyboard behaviors. http://w3.org/TR/css3-ui > This might be a > little extreme, but maybe...? It would involve figuring out which > element would get the event, The element that is :focused perhaps? > or maybe limit them to a subset of > elements. I dunno. Haven't really thought it out, but I thought I'd > just bring it up. Thanks for bringing it up. I don't have a good idea of how keyboard events would be translated to selector states yet, but perhaps someone else will. Tantek [1] http://lists.w3.org/Archives/Public/www-style/2001Oct/0092.html I couldn't help but note what brought on that thread, that Vadim Plessky claimed that "Konqueror browser ... will be fully compliant with CSS2 in 1 year time frame". Note: as the URL implies, that was 2001 October. Hey, how's it going Mr. Plessky? (cheapshot) > > On Thursday, February 20, 2003, at 12:48 AM, Tantek Çelik wrote: > >> >> On 2/19/03 9:33 PM, "Chris Vincent" <dris86@cox.net> wrote: >> >>> >>> I've always thought it might be useful to be able to do >>> pseudo-elements >>> for events other than MouseOver. For example, you could have >>> MouseDown, MouseUp, etc. >> >> For example, you have :active >> >>> Its functionality would be limited, but could >>> really ease up the JavaScript use on simple interaction. >> >> Very much agreed. >> >>> You could do >>> rollovers and such with a simple change to the background image. >> >> And many folks have. Just search for CSS rollovers: >> >> http://www.google.com/search?q=CSS+rollovers >> >>> If >>> :hover can make it into CSS, why not some others? >> >> Agreed, and plenty others have. See "Selectors", specifically the >> section >> on UI selectors: >> >> http://www.w3.org/TR/css3-selectors/#UIstates >> >>> >>> "Intel Inside" - The World's Most Common Warning Label >> >> Funny, I thought the world's most common warning label was: >> >> "Copyright. All rights reserved." >> >> Tantek >> >> > > "Clearly, if people use the same word with subtly different meanings, > but they think they mean the same thing, communication is just noise." > ~ Fëanor from iDevGames.com forum > [ Random Signature #15 ] >
Received on Thursday, 20 February 2003 19:09:57 UTC