|
Posted by Andy Dingley on 04/10/07 15:35
On 10 Apr, 15:46, Grant Robertson <b...@bogus.invalid> wrote:
> Thank you. They must have had it fixed before you looked at it. Read my
> other message.
Change host. I can't imagine why they do / did this. I can't imagine
why it should affect the DNS either. There is no way I would ever use
a host that did this sort of mangling to my source.
> > PS - don't use <a name=..." >, just use the id attribute on an
> > existing element.
>
> Why? Is <a name=..." > deprecated now? Or just out of fashion.
> I'll give it a try.
It's obsolete, although not formally deprecated. id is a good
replacement for it, and works with all browsers of current interest.
Life is easier if you just use id on existing elements (as you're
already doing in many locations), there's no drawback to doing so
(although someone will undoubtedly post one in a moment).
<http://www.w3.org/TR/html4/struct/links.html#edef-A> is the obvious
reference material to read.
> > Your markup isn't (fortunately) XHTML. Use HTML 4.01 Strict instead
>
> Why do you say it fortunately isn't XHTML?
Because it just isn't XHTML (Your posting claimed it was, your HTTP &
HTML disagree. Maybe your host has fiddled with that too?).
Because it's not a good idea to use XHTML, except in some pretty small
contexts.
Because if you're asking, it's not a good idea for you (many, many
messages passim).
> It is over 7 years old now. Even Microsoft should have caught up by now.
They should, they haven't, QED.
> > Your markup is very broken. Use a validator.
>
> I use the validator in Dreamweaver MX 2004. It validates fine.
Then your validator is broken. Your code certainly is.
It doesn't even look like markup that was broken by any conceivable
automatic process that your host might be doing to it.
> I suspect
> that my free hosting service is taking my code and processing it to
> insert their popups.
Quite possibly. I think it's broken outside of this though.
Navigation:
[Reply to this message]
|