Strict w3c validation allows any data-* attributes, and any class. Directives can be applied to DOM elements with any of: <tag directive-name> <tag data-directive-name> (*) <tag x-directive-name> <tag directive_name> <tag x_directive_name> <tag data_directive_name> At least the data- one is fully W3C compliant (provided you declare HTML5 doctype). So the following code validates (the attribute name, … Read more
Did you include the semi-colon after &? Your link should be <a href=”https://stackoverflow.com/questions/15970738/index.php?option=com_content&view=article&id=6&Itemid=4″> Note that if you paste this url into the address bar of your browser it won’t work – the browser converts the & into & when you click the link in the page.
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
Try putting your javascript inside a CDATA block like this: <script type=”text/javascript”> <![CDATA[ // content of your Javascript goes here ]]> </script> which should make it pass validation. To be extra safe you can add Javascript comments around the CDATA tags to hide them from older browsers who don’t understand the CDATA tag: <script type=”text/javascript”> … Read more
The title element is indeed required, but as Jukka Korpela notes, it also must be non-empty. Furthermore, the content model of the title element is: Text that is not inter-element whitespace. Therefore, having just a space character in the title element is not considered valid HTML. You can check this in W3C validator. So, an … Read more
That’s because you are nesting a block level element inside the p tag which is invalid. You can only nest inline elements such as span, a and img inside p tag. So your markup is invalid, consider making something like <div class=”inr_content clearfix”> <div class=”col2 first fl”> <p>to provide a drive-in services.</p> </div> <div class=”col2 … Read more
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”]’.
<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!
While it’s true that the W3C’s HTML spec does not define it, there is an allowTransparency attribute, and it is supported by all modern browsers (and Internet Explorer). As HTML5 has taught us, the cart is supposed to be before the horse. Suppose you have this HTML on your main page, index.html: <html> <body> <iframe … Read more
Yes, it’s valid and works fine. This attribute explicitly associates the label being defined with another control. http://www.w3.org/TR/html401/interact/forms.html#h-17.9.1