Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
I’m not sure that I’m completely understanding what you posted, but it seemed like the validator was asking for the type attribute for the script tag which was not supplied. I think language is deprecated in XHTML. Not 100% sure on this.
Make sure your DOCTYPEs match your syntax. You’ll get a ton of headaches otherwise.
Firefox is very picky about certain things like that, for example if you are using inline table width and height attributes Firefox completely ignores them if the DOCTYPE is XHTML strict. I had some legacy content in our CMS that got massively hosed when we tried to transition to XHTML strict. We ended up just sticking with Transitional.
Shoving is the answer – pusher robot
Offline
#14 2005-06-09 21:11:19
- marios
- Archived Plugin Author
- Registered: 2005-03-12
- Posts: 1,253
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
I am using Firefox 1.04 with all the Developper extensions installed.Under Tools(or ctrl+ shift +a) there is a validate Local HTML option where I use it to debug my page templates.It will call the W3C v0.67 validationservice under the following URL
So I have removed all the invalid markup(no tables no fancy attributes) and it will not validate.
If I will call the service for www.zeldman.com in the same way it will return exactly the same errors as described above and zeldman will not validate if you call the service in the way I describe above.
Since I am not validating against XHTML strict(using Transitional Doctype) the language attrribute should be deprecated but still allowed.
Does that not pretty much look like a bug in the validation service ?
regards, marios
Last edited by marios (2005-06-09 21:18:47)
⌃ ⇧ < ⎋ ⌃ ⇧ >
Offline
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
>I still don’t understand the “center” issue, I guess because I don’t understand why you are using a depracated “center” tag. I would prefer to keep >documentation focused on XHTML strict. I think if you use a division (div) correctly (or perhaps even a class attribute) to center a particular string >of text, then you don’t have validation problems.
It is? Bugger I did’t know that – it does validate 1.0 strict w the centre though, once I add the spaces so..dunno
Offline
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
Hmm Zeldman validates fine for me using the local html option of the Web Developer’s toolbar. Thats pretty curious behavior though if it validates with one request and not the other.
About language from the validator snippets you quoted it doesn’t seem that’s it’s complaining that language is present but that type is missing. try adding type =“text/javascript” to your < script > tag and see what happens.
Shoving is the answer – pusher robot
Offline
#17 2005-06-10 22:51:29
- marios
- Archived Plugin Author
- Registered: 2005-03-12
- Posts: 1,253
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
Found out what it is,It’s the stupid propriety code that NIS inserts there to suppress the product generated error messages.
Oh man, that means that anyone who sit’s behind a symantec firewall can not get a site validated.
regards, marios
⌃ ⇧ < ⎋ ⌃ ⇧ >
Offline
Re: [wiki] Roundup of Common XHTML Validation Problems/Solutions...
Not that I’m discrediting these as real problems, but I think they are kind of peripheral to what this thread is about, which is mainly common validation issues that come up from using core — or close to the core — Textpattern itself.
Offline