I saw some pretty templates here that is not a valid HTML /XHTML, I used W3C to validate some of the templates and Im wondering why still accepted and labeled as Valid HTML “Yes”, I think TF should be strict on this. BTW Im just wondering.
There are a few instances where I’ll personally accept a template if it isn’t valid CSS . Many people use some browser specific stylings in their themes – like:
A stylesheet won’t validate because of this line. But, I’ll still accept it.
Can you email me a link to one of the templates that doesn’t have valid HTML ? email@example.com
I just wanted to mention here that Blogger templates (the XML based, widgetized style) are IMPOSSIBLE to create with valid XHTML /HTML. That is, the templates themselves may be valid, but when generated as an active blog (seen in the browser), the generated pages are invalid.
Believe me, I’m not just saying this because I design Blogger templates to sell here!
The reason is because Blogger generates extra code in the source which is formed server-side (not from the template code) and is invalid.
This extra code is generated to make all widgetized sections function, and can mostly be seen near the bottom of the source code for each generated page.
We have no control over this extra code, and even though most Blogger users would prefer to be able to create valid HTML in their blogs, it doesn’t seem that this issue will be remedied any time soon.
Classic Blogger templates (non-widgetized) can be made to have valid HTML when generated. However, Blogger is decreasing support for this type of template, and most Blogger users prefer the widgetized versions anyway.
I do hope this will not affect the Blogger templates which some of us design for Theme Forest!?
Jeffrey, please let me know if you need any more info about this in regard to Blogger.
^ The same thing happens when you embed widgets from flickr. My personal blog template is 100% valid but because of my flickr photos in the sidebar it throws tons of errors when you try to validate.
That’s interesting to hear about Flickr. That’s why I rarely use the provided widgets. It’s always better to work with the API yourself.
Speaking of which; Does anyone want to write a quick tut for the blog that shows how to display your Flickr photos on a template (without using Flickr’s provided widget, of course.)? We’ll pay you $60.
Email me at firstname.lastname@example.org if interested. PHP would probably be best – considering its popularity on this site.
my understanding of a valid XHTML /CSS is that the main, core code is standard.
If there are things like
moz-border, -webkit..., etc. This doesn’t matter as it is just browser specific.
The main point that should be taken on this is that the structural code itself it correct.
I would agree validating your templates is really important but as always there is exceptions to any rule. I get an error for not declaring the size of my textarea in forms with row/col using strict XHTML but made a conscious decision to have that done in the stylesheet. I think it makes it a bit easier for potential buyers to modify the template.
- United States
- Was featured in a podcast
- Attended a Community Meetup
- Author had a Free File of the Month
- Bought between 50 and 99 items
- Repeatedly Helped protect Envato Marketplaces against copyright violations
- Has been a member for 5-6 years
- Contributed a Tutorial to a Tuts+ Site
- Contributed a Blog Post
@Shadow- Couldnt you just insert the rows and cols and leave them blank and then style with css
Or will this not validate under strict?