- From: Dave Salovesh <darsal@tezcat.com>
- Date: Thu, 17 Jul 1997 17:44:57 GMT
- To: www-html@w3.org
Walter sent this to the www-html list: >So, how about assigning a selection-style to the <INPUT> element? >Something like: { selection-style: invert } > >Perhaps selection-style values of: > > hilite | dim | invert | sink | exchange > >although I'm not sure how exchange would interact with PRESSED attribute. I'd like a two-frame image file, where the second frame is only shown when the button is pressed, please. Hold the fries. Yes, I think placing the appearance of buttons in style sheets somewhere is the way to go. This brings up a question. When will we see an extended CSS? I'm a little worried that adoption of the BUTTONs in this HTML specification will result in forms which cannot work with any browser in use today. I'd like to argue that button functions be made into pseudo-classes, so they can be applied not only to SUBMIT buttons but to CHECKBOXes and RADIO buttons as well. Imagine toolbars and radio buttons that actually look like toolbars and radio buttons! I'd even like to make a case for a CSS { button } property group applicable to replaced elements that could give a pressed button look to images used as a navbar in a framed document. But I'm not sure if the CSS&FP WG is doing anything on a coordinated schedule that would make this idea anything but a good theory. Could the HTML WG pass the BUTTON to CSS? -- dave salovesh darsal@tezcat.com
Received on Thursday, 17 July 1997 13:44:51 UTC