Re: W3C validation error

Re: W3C validation error

am 19.12.2007 04:24:53 von dorayme

In article ,
Toby A Inkster wrote:

> dorayme wrote:
>
> > On the other hand, I notice that you have a but no in
> > your last table. This you may not want to have?
>
> Even with the strict DTD, that's perfectly valid.

Hence my weasel words "This you may not want to have?". With JK's
eagle eye, I cannot afford the least carelessness.

> The TBODY element is
> implicitly opened as soon as a TR element is encountered that is not
> enclosed in a THEAD or TFOOT element. The content models of the various
> table-related elements given in the strict DTD are:
>
> > (CAPTION?, (COL*|COLGROUP*), THEAD?, TFOOT?, TBODY+)>
>
>
>
>
>
>
>
> > cell-->
>
> You'll notice that TABLE *must* contain a TBODY and cannot contain a
> TR. Thus any TRs that are not part of the THEAD or TFOOT automatically
> begin the TBODY element, which has an optional opening tag. So the
> following is a valid TABLE element:
>
>


>
>
>
Hello
>

>
> Such tables may be undesirable though, so it may be a good idea to create
> a custom DTD that tightens up the rules for opening and closing tags for
> table-related elements.

About:

"http://www.w3.org/TR/html4/strict.dtd">


Lineupnumberedheadings





Hello




My BBEdit says:

Error: Close element “” found but element wasn't open.
Warning: Element “” implicitly closed here.
Warning: Element “” implicitly closed here.

I am happy about the warnings (these can be controlled to some
extent from Preferences/HTML Tools. But the *error* slightly
disturbs me after reading your above?

--
dorayme

Re: W3C validation error

am 19.12.2007 04:45:39 von dorayme

In article
,
dorayme wrote:

> My BBEdit says:
>
> Error: Close element “” found but element wasn't open.
> Warning: Element “” implicitly closed here.
> Warning: Element “” implicitly closed here.

Actually it said:

Error: Close element found but element wasn't open.
Warning: Element implicitly closed here.
Warning: Element implicitly closed here.

--
dorayme