w3c-validation

HTML5 ambiguous ampersands in URLs

由 ☆樱花仙子☆ 提交于 2019-12-07 20:32:20
问题 The W3C Validator is firing up an error about ampersands in some of my URLs. For example: <link href="min/?f=static/css/reset.css,static/css/main5.css&2" rel="stylesheet"> According to the HTML5 spec, however, the validator is wrong: An ambiguous ampersand is a U+0026 AMPERSAND character (&) that is followed by one or more alphanumeric ASCII characters, followed by a U+003B SEMICOLON character (;) , where these characters do not match any of the names given in the named character references

Does a .NET library for the W3C Markup Validator API exist? [closed]

由 怎甘沉沦 提交于 2019-12-07 15:00:38
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . I'd like to validate that users of my WPF application are putting proper XHTML into its TextBox control. I found that there's an API for the W3C Markup Validator. It's web page says: Building of libraries used to interact with the validator's API is encouraged. … and it lists known Perl, PHP/PEAR and ColdFusion

Angular2 syntax in W3C HTML Validator

由 ▼魔方 西西 提交于 2019-12-07 10:08:17
问题 Angular 1.x allowed to put elements in HTML, which were not known for W3C HTML Validator. Workaround for this was to add data- prefix and write e.g. data-ng-repeat instead of ng-repeat . In the current Angular 2 version we have a different syntax. This syntax is also case-sensitive, e.g. we have to use ngClass , not ngclass . All brackets used in Angular2 are causing HTML validation errors. Fortunately there is also a canonical form, so instead of (event) we can go with on-event , instead of

W3C Validation and Vue's HTML binding syntax

由 不打扰是莪最后的温柔 提交于 2019-12-06 23:09:04
问题 When I validate my page with the W3C validator, I get this error with Vue's event and binding syntax: Error: Attribute v-on:click not allowed on element div at this point. Is there a way to fix this? 回答1: They would ideally support the use of data-* attributes, e.g., data-v-on:click , but it seems they don’t. See their issue Why not using HTML5 data-* attributes. It seems that it was possible to overwrite the used prefix, but this option seems to have been removed. 回答2: You can create a

W3C validator: “Bad value robots for attribute name on element meta”

由 纵然是瞬间 提交于 2019-12-06 11:31:07
What has changed with <meta name="robots" content="index,follow"> meta tag? I use HTML5 and W3C validator marks my page as invalid. There is robots meta name allowed in http://wiki.whatwg.org/wiki/MetaExtensions . Exact validator error: Bad value robots for attribute name on element meta : Keyword robots is not registered. unor The validator is wrong. The robots name is registered according to HTML5’s rules , so you can use it. You’ll probably see the same problem with all other registered names, too (e.g., with the google name ). 来源： https://stackoverflow.com/questions/22100619/w3c-validator

How to solve HTML5 validation error on fb-like box?

由 拥有回忆 提交于 2019-12-06 06:53:40
问题 How to solve this HTML 5 validation error related to Facebook like button? Here is the text from validation engine: Line 3170, column 261: Element name fb:like-box cannot be represented as XML 1.0. …rue" border_color="" stream="false" header="false" height="260" ></fb:like-box> Here is the code on Line 3170: <div id="fb-root"></div><script src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like-box href="http://www.facebook.com/fburlhere" width="250" show_faces="true" border

Does a .NET library for the W3C Markup Validator API exist? [closed]

由 一曲冷凌霜 提交于 2019-12-06 05:09:05
Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . I'd like to validate that users of my WPF application are putting proper XHTML into its TextBox control. I found that there's an API for the W3C Markup Validator . It's web page says: Building of libraries used to interact with the validator's API is encouraged. … and it lists known Perl, PHP/PEAR and ColdFusion libraries. Does anyone know of a .NET library for the W3C Markup Validator API? Does one already exist?

W3C validation for complete site [closed]

由 泪湿孤枕 提交于 2019-12-05 20:25:38
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 9 months ago . I am working on a project where I have to validate the complete site, which has around 150 pages, through W3C Markup Validation. Is there a way to check W3C Markup Validation of an entire website? 回答1: The W3C doesn't offer this on w3.org. http://validator.w3.org/docs/help.html#faq-batchvalidation But you can

Angular2 syntax in W3C HTML Validator

由 随声附和 提交于 2019-12-05 12:23:08
Angular 1.x allowed to put elements in HTML, which were not known for W3C HTML Validator . Workaround for this was to add data- prefix and write e.g. data-ng-repeat instead of ng-repeat . In the current Angular 2 version we have a different syntax. This syntax is also case-sensitive, e.g. we have to use ngClass , not ngclass . All brackets used in Angular2 are causing HTML validation errors. Fortunately there is also a canonical form, so instead of (event) we can go with on-event , instead of [property] we can go with bind-property and instead of [(ngModel)] we can use bindon-ngModel . All

Why does the W3C RDF validator replace the RDF URI with its own?

由 荒凉一梦 提交于 2019-12-05 10:37:34
Let us say that we input the following RDF code to the W3C RDF validator at http://www.w3.org/RDF/Validator/ . <?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:uni="http://www.example.org/uni-ns#"> <rdf:Description rdf:about="949352"> <uni:name>Grigoris Antoniou</uni:name> <uni:title>Professor</uni:title> </rdf:Description> </rdf:RDF> Once I ask to parse the RDF code, I find that in the triples, the RDF URI has been replaced with the own URI of the validator. Should not the subject of the
订阅 w3c-validation