Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

HTML

HTML Email Not Valid

Hello

I just knew that the html I created based on treehouse html email class is not passing the W3C validator.

Should this be a concern or not really cause just email?

Anyone? I searched this forum but no results on the subject :)

5 Answers

It depends on errors.

If it's saying don't do inline styling, you're good to go. but If it's about tag closings you should check it out...

If you need more help, put your design in a github repo and use the raw file in w3 validator and put the final link here...

Hi Hossein, It's various errors. I tested the original lesson file got 33 errors and mine got 21 :D I haven't read them all but the tag closing (I was expected to see that too actually) is not really the main. One really caught my attention is the use of <center>, and many other like the use of attributes like width, height etc like height="100%". I've been trying to switch from one doctype to another.

But it's true though, if i try to validate the non-inline styled there are less errors. I'm just thinking maybe because with html email the main idea is to make it work using whatever way possible.

Is it really? What do you think? Should an html email having a valid markup, or not really the main concern as the way it is done is already totally opposite of what we should do when creating normal website.

Try deleting height,width attributes from html and adding it to inline css.

sometimes for some reasons we use vendor prefixes which W3 jigsaw Validator call them Errors! It can be something like that.

I know It's good to be a responsible man/woman and listen to standards, but if you are getting the result that you want and the errors are silly things like what i've said before, ignore the errors. Check Google for instance!

Yes, I agree with you, sometimes its just ridiculous and not really necessary. Thanks at least I know I'm not 'off' to think that it is not that important. It is, but not that.

No wait I found out yay! So everything about width, height must be in css that's it. Then it will be valid. So somehow i think the tutorial file about this needs to be checked? Hello, Mike the Frog? :)