|
|
Posted by Yogi_Bear_79 on 10/17/06 16:29
"Andy Dingley" <dingbat@codesmiths.com> wrote in message
news:1161093989.817337.305310@k70g2000cwa.googlegroups.com...
>
> Yogi_Bear_79 wrote:
>
>> I'm using DreamWeaver, and not the GUI, just the code side. I ran the
>> validator as well, 90% of the items it is flagging appear to be correct
>> when
>> I manually look at the code.
>
> Here's a clue. Either the validator is getting it grossly wrong, or
> you're getting it wrong somewhere and you just haven't seen it yet.
> Your call.... We get a _lot_ of W3C Validator bug reports in this ng,
> yet it seems to need awfully few fixes.
>
> And a hint - validators rarely report errors, they usually report the
> first point _afterwards_ when the document became provably invalid
> after an earlier error. So if you can't see what the error was, start
> looking where it was reported, then scan back upwards through it.
>
This line and others like it account for a vast majority of the validators
erros on my page, but I don't see the problem. I assume the validator is
correct and I am not, but could use some guidence on correcting my code.
This portion of my page was retrieved from an on-line tutorial on using
includes to design a menu system. It may be antiquated ideas, but it does
work for me, but I would rather do it right. Your time is appriciated
mymenu2.addMenu("home2","<b> Home  </b>")
Line 40 column 55: end tag for element "B" which is not open.
mymenu2.addMenu("home2","<b> Home  </b>")
Navigation:
[Reply to this message]
|