w3c markup validator ampersand (&) error
for each & sign you got write & in your example it would be: c91588793296e2?s=50&d=http%3A%2F%
for each & sign you got write & in your example it would be: c91588793296e2?s=50&d=http%3A%2F%
I found some entry from: Markup Validation Error: “Attribute name not allowed on element at this point” error #HTML5 Just in case you intend to define a custom attribute, you have to prepend the attribute with “data-“. So in this case, name would be: data-name=””. And you can reference it by ‘div[data-name=”value”]’.
URL encode the | (pipe characters) in the href attribute (%7C): <link rel=”stylesheet” type=”text/css” href=”http://fonts.googleapis.com/css?family=Open+Sans:400,600,300,800,700,400italic%7CPT+Serif:400,400italic%7CBree+Serif”>
You could use the data- html5 attribute which is standard and as far as I know works the same for Angular. Something like: data-ng-app=”” data-ng-init=”xxx” Will work the same in Angular and are validated by W3C. Look also at this: ng-app vs. data-ng-app, what is the difference? Aside from that, from my experience working with … Read more
Well I posted a comment but no love. You can achieve a W3C valid button by simply putting an image inside the button. Fiddle Granted you’ll have to create your images and add the text to them. But since you’ve already created images for the corners that shouldn’t be too hard. Also image sprites are … Read more
<html xmlns=”http://www.w3.org/1999/xhtml” xml:lang=”en”> <head> <title>test</title> </head> <body> <table> <tr> <td> <div>content</div> </td> </tr> </table> </body> </html> This document was successfully checked as XHTML 1.0 Transitional!
Here is a good article from the MDC which explains the problems (and solutions) to form autocompletion. Microsoft has published something similar here, as well. To be honest, if this is something important to your users, ‘breaking’ standards in this way seems appropriate. For example, Amazon uses the ‘autocomplete’ attribute quite a bit, and it … Read more
Either: Add a heading (h1, …, h6) tag to your section element. Replace your section element with a div element. Ignore the warning. The message you’re seeing is a non-normative usage recommendation, as per the HTML5 spec (highlighting mine): The theme of each section should be identified, typically by including a heading (h1–h6 element) as … Read more
Only inline elements may be contained within inline elements. span is an inline element. So, tags like a, img, sup, etc. can go within a span, but block level elements like div and p cannot. UPDATE In reality, different elements which default to inline display behave differently. Some “inline” elements may allow block elements (a … Read more
“CSS class” is a misnomer; class is an attribute (or a property, in terms of scripting) that you assign to HTML elements. In other words, you declare classes in HTML, not CSS, so in your case the “target” class does in fact exist on those specific elements, and your markup is perfectly valid as it … Read more