Cheers,
it makes sense now.

So the H1 tag is not allowed in the anchor.

<a name="t67"><h3>FusionMX Methodology</h3></a>

I gues it should be 
<h3><a name="t67">FusionMX Methodology</a></h3>

yes yes yes, thats also why the funny hovering thing happens, because I have 
a:hover
{
        blah blah
}
in my stylesheet.

I guess the only way to overcome that is to create a class instead, which is annoying.
a.href:hover
{
        blah blah
}

BTW. does anyone understand what I was trying to get at earlier with the selecting 
text issue?
I myself select paragraphs when reading a webpage that is a bit cluttered or not easy 
to read, I reckon people with visual disabilities will do this even more.
Does anyone else select a paragraph while reading it, i.e. making the background dark 
blue and the text white.


Taco Fleur
07 3535 5072
Blog: http://www.tacofleur.com/index/blog/
Methodology: http://www.tacofleur.com/index/methodology/
Tell me and I will forget
Show me and I will remember
Teach me and I will learn


-----Original Message-----
From: Mark Stanton [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 January 2004 2:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [WSG] document type does not allow element error


Validation saves the day again!

That issue with the unclosed <a> is exactly what the validator is tripping
on. I always wondered what was going on with the hover state of you page....

I'll chuck together something quick on reading the DTD, but there is a
serious issue with the current validator - its messages are very difficult
to understand.

Luckily W3C are working on a new validator that will help in this area.
Check out
http://validator.w3.org:8001/check?uri=http%3A%2F%2Fwww.tacofleur.com%2Finde
x%2Fmethodology%2F&verbose=1&fussy=1

---------------
The mentioned element is not allowed to appear in the context which you've
placed it; the other mentioned elements are the only ones that are allowed
there. This might mean that you need a containing element, or possibly that
you've forgotten to close a previous element. The most common cause for this
message is that you have attempted to put a block-level element (such as
"<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or
"<font>").
---------------

That makes a little more sense doesn't it.


Cheers

Mark


------------------
Mark Stanton 
Technical Director 
Gruden Pty Ltd 
Tel: 9956 6388
Mob: 0410 458 201 
Fax: 9956 8433 
http://www.gruden.com
*****************************************************
The discussion list for http://webstandardsgroup.org/
*****************************************************

Reply via email to