Re: BUTTON element

Chris Wilson (cwilso@MICROSOFT.com)
Thu, 17 Jul 1997 08:21:32 -0700


Message-ID: <41F7F4CE3CA2CF11BC5000805F14B2A9023ABF70@RED-31-MSG.dns.microsoft.com>
From: "Chris Wilson (PSD)" <cwilso@MICROSOFT.com>
To: "'Lee Daniel Crocker'" <lee@piclab.com>, walter@natural-innovations.com
Cc: www-html@w3.org, www-style@w3.org
Subject: RE: BUTTON element
Date: Thu, 17 Jul 1997 08:21:32 -0700

Actually, the point of the BUTTON tag is to allow rich content (e.g.,
images and marked-up text) in a button - which INPUT is incapable of,
since it is not a container.

	-Chris
Chris Wilson
cwilso@microsoft.com
***

> -----Original Message-----
> From:	Lee Daniel Crocker [SMTP:lcrocker@calweb.com]
> Sent:	Wednesday, July 16, 1997 11:11 PM
> To:	walter@natural-innovations.com
> Cc:	www-html@w3.org; www-style@w3.org
> Subject:	Re: BUTTON element
> 
> > OK, here's another idea. I use a RAD environment on the Macintosh
> called
> > FaceSpan [1], which has a pictbox property called 'selection style'.
> The
> > property values are as follows:
> > 
> >    none                 pictbox or cell does not highlight
> >    by hilite            white areas of pictbox or cell are overlain
> >                         with the System highlight color (from the
> >                         Color control panel)
> >    by invert            colors of pictbox or cell are inverted
> >    by lasso             colors of pictbox or cell are inverted
> within
> >                         contours that exclude the pictbox's fill
> color
> >    by frame             pictbox or cell is surrounded by a frame
> >    by sink              pictbox or cell is surrounded by a column of
> >                         pixels on the left and one row of pixels on
> >                         the top
> >    by exchange          a different artwork resource is used for the
> >                         highlighted pictbox
> > 
> > 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.
> > 'dim' would simply darken the colors: FF->99, CC->66, 99->33,
> 66/33/00->00.
> 
> Much, much, better than that hideous, incompatible BUTTON tag.  If one
> absolutely /has/ to break compatibility for a feature, that's fine,
> but
> this is not anywhere near such a case: <INPUT> works just fine, and
> its
> display attributes belong in a style sheet--even the X,Y argument is
> uncompelling, because they can be ignored easily.