sideshowbarker

Reverted https://github.com/validator/validator/commit/43e8f992d5adc62c6e2a4bbf65734f14e344da1a

To provide some context here about the relationship of OWD to MDN and about my own role in all this: OWD funds the work of a group of writers, whose...

> @sideshowbarker Please stop hiding or deleting comments in this repository. Thank you! Lest anyone else here be led to believe I hid or deleted any comments nefariously or something:...

I agree it could be great to have a WebAssembly version of the validator, but there’s very little chance I’d be able to make time myself any time soon to...

I’m going to (reluctantly) close this issue — because, after spending some time investigating it myself, my conclusion is that it’s currently not possible to convert vnu into WebAssembly, and...

Would love to add this. I guess this would go a bit beyond the typical kind of checks that most users expect a “markup validator” to do (e.g., what the...

> For CSPs delivered through `meta` we can at least enforce whatever is enforceable from the https://html.spec.whatwg.org/#attr-meta-http-equiv-content-security-policy, and notify of the risks having `` or `` before 'meta' containing CSP....

The relevant requirement is here: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fs-action > The `action` and `formaction` content attributes, if specified, must have a value that is a [valid non-empty URL potentially surrounded by spaces](https://html.spec.whatwg.org/multipage/urls-and-fetching.html#valid-non-empty-url-potentially-surrounded-by-spaces).

See my comment at https://github.com/validator/validator/issues/398#issuecomment-259023870 In the current checker architecture and given the extreme complexity of the ARIA role requirements, it isn’t practical to produce a better error message here—especially...

I can reproduce the inconsistent reporting behavior from the issue description, but at this point I have no idea what’s causing the inconsistency. Some further investigation is needed.