[Javascript] Re: Standards

David Lovering dlovering at gazos.com
Fri Apr 11 21:15:15 CDT 2003


Hmmm... maybe I should get out more...

Admittedly, most of the text elements I work with are jiggered via their CSS
font characteristics, so I was perhaps speaking a bit more ex-cathedra than
necessary...  I was able to confirm that <font> is on the way out --
probably as a sop to the rapidly moving integration of XML and HTML.  On
this point I stand corrected.

More importantly, the size parameter IS supposed to be a relative index
(+/-)[0-7].  Amazing that the thing didn't blow up in my face.  Next time
I'll stand behind a blast shield.

On the subject of BUTTON, if you'll scope out the description on page 383 of
the HTML 4.0 Sourcebook, you'll note that LEGEND is listed as one of the
attributes assignable to BUTTON.  I believe the W3 document backs me on
that, but I'll check to make certain.  Anyhow, it operates as the
description of LEGEND suggests it should, and BUTTON is doing for <INPUT
TYPE="BUTTON"> what CSS style.font is doing for <FONT>.   There are various
examples in the literature of this in use, so if I am confused, at least
I've got buddies.  [And yes, I did use it correctly -- it is bounded by the
<BUTTON></BUTTON> tags].

Another non-canonical usage I got caught with was the use of type='image'
within a <BUTTON> tag.  While it works in IE6, it is plainly a fluke, as it
isn't part of their core syntax. Everyone I talked to suggests that the more
portable (and correct) implementation is

<BUTTON>
  <IMG SRC='myButton.gif' ...>
</BUTTON>

I'll begin retrofitting my code immediately to reflect this.  [If I ever
recall where I got the other style of definition, I'll beat on it with a
stick].  Mea Culpa.  Probably some jerk-ass M$oft tech note I glommed onto
during my misspent youth.

The layering is still managed a bit differently between IE and NN.  I hope
that this is resolved soon, and a lot of folks seem optimistic on this
score.

About the only defense I can use to justify my getting dragged onto this
topic is that JavaScript is rapidly becoming a prototyping language for HTML
, and should therefore have tools for manipulating, creating, and removing
every object type within the base specification.

Thanks for the wake-up call!  I just gave myself three smeech-smeeches in
response.  I'll start sleeping with a W3 spec under my pillow for the
foreseeable future.

-- Dave Lovering




More information about the Javascript mailing list