Re: draft-ietf-html-table...

Lou Montulli (
Thu, 3 Aug 95 22:01:48 EDT

>> I think the draft spec should avoid the conflict with BORDER and
>> use BORDERSTYLE or something similar. We have been very good
>> about not introducing conflicts between any of our extensions
>> and existing specifications and would appreciate the same in return.
>Then how do you explain <CENTER>, which is different than <? ALIGN=CENTER>
>that was proposed *and* implemented by other browsers before you introduced
><CENTER>? And why do you still advocate its use? [1]

<CENTER> does not conflict with <? ALIGN=CENTER> in any way and contained
more functionality than the latter. Now that <DIV ALIGN=CENTER> exists
it will be implemented and used preferentially

>Also, <TABLE BORDER=0> will give a border on browsers which implemented
>the proposed table specification [2], which is different than Netscape's
>behavior [3]. I think a better way of introducing this experimental
>extension would have been to introduce a BORDERWIDTH attribute, or,
>better yet, implement style sheets and add all the fancy formatting
>stuff you want there.

BORDER=0 is a "border" case. Since we allowed for an integer value
we had to have some behavior when it was set to zero. People should
not use BORDER=0, they should instead be leaving BORDER out entirely
since that will render correctly in all browsers.

>I'm sorry if this is somehow "out of line", and I don't mean to start a
>flamewar, but I find the paragraph quoted above extremely hard to accept.
>> Since there are lots of people using BORDER in current documents
>> they obviously find it useful, therefore you should consider adding
>> BORDER as well as BORDERSTYLE to the table spec.
>Would this argument carry the same weight if we changed "BORDER" to "BLINK"?

Yes, if blink is useful, as many people think it is, then it should be
supported somehow. Who are we to say that blinking text is completely
evil and should never be allowed? Others feel the same way about
images as blink, should they be allowed to outlaw images?

>I'm not suggesting that these two things are somehow equal to each other,
>only that the decision to add something to HTML should be based on its own
>merit rather than the degree to which a particular non-standard extension
>has been used by people who are knowingly playing with experimental HTML.

Because it is in wide use it should be seriously considered for it's
merit. While considering it's merit you should try to understand the
point of view and intensions of the people using it. It is definatly
a style attribute, but does it belong in HTML or in a style sheet.
Opinions vary...


Lou Montulli       
       Netscape Communications Corp.