On Mon, 5 May 2008 19:19:40 -0500, Dolores Park wrote (in article
<brddYgxvE0gm-pn2-6I6Hd78kudeq@[EMAIL PROTECTED]
>):
[responding to my opening posting in this thread]
> Your question (and the ensuing discussion) arises from an incorrect use
of
> terminology.
>
> There is not a single button present on your ECR page. I assume that
what
> you're referring to as "buttons" are the menu items toward the top of
that
> page. They are links (HTML 'ANCHOR' elements) implemented using GIFs.
> Links have long had several states to emphasize them such as "over",
> "visited", etc. When implemented as text, the change in emphasis is
> automatic; in the case of a graphic link, javascript is needed to
change
> the image to reflect the link's state.
The ECR site under discussion was implemented in Freeway Pro 5, a WYSIWYG
website implementation application produced by SoftPress, a British
company.
The Freeway tools and the Freeway do***entation refer to those seven "menu
items" as "buttons".
> HTML 'BUTTON' elements typically conform to the user's expectations of
how
> a pushbutton should look and act (e.g. they move up and down). Buttons
are
> usually used in forms ("Submit", "Clear", etc) and are almost never used
> as links. Historically, buttons have never had an "over" state.
> Late-model browsers may implement it, but only as a convenience for the
> javascript programmer, not to provide visual emphasis for the user.
Also, the Freeway tools and do***entation refer to the three states of a
"button" as "Normal", "Mouse Over", and "Click".
> So, to answer your question, there is an agreed upon standard for button
> behavior but only a generally accepted convention for links.
So it looks like that there is unfortunately some disagreement in the
website
development community over terminology.
--
James Leo Ryan ..... Austin, Texas ..... taliesinsoft@[EMAIL PROTECTED]
|
