The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: validation errors
I just checked my directory page and saw a shed-load of validation errors. One example is a <p> element nested in a <span> element. Now, I’m not a coder I admit, but I don’t think that I would do that.
Some validation problems I can live with but I don’t like that one.
Yes, I am aware of validation errors. These vary depending on which doctype you run it thru. The majority fall into it complaining about legacy table attributes, use of short tags which are just self closing tags and are valid HTML5, the use of the data node which is valid HTML5, and a bunch generated by Google for their maps. The biggest no, no is that <p> tag which I should fix.
Really, the important thing is that everything displays properly across the various browsers. I use to spends hours on end making sure this was perfect to a tee only to have layouts break when used within the many thousands of themes in use. Most of the CSS and tables attributes were added only to ensure proper display in as many themes as possible while providing the broadest support for browsers as possible.
You cannot reply to this support topic. Please open your own support topic.