Nick Schonning comments

Results 645 comments of


                                            Nick Schonning

redirects for google URIs not working correctly

Related to https://github.com/validator/validator/issues/753

[CSS] Token after BOM can’t be `whitespace`, `at` or `EOF`

Probably something upstream at https://github.com/w3c/css-validator

<meta name="viewport" content="width=device-width, initial-scale=1.0"> is checked as wrong

The message is a little confusing, but it's because you have the meta tag in the ``, rather than the ``

W3C Validator -> Warning "aria-label"

https://www.w3.org/TR/using-aria/#firstrule look at if you can use native elements before you start look at using ARIA

Incorrect validation of css calc in combination with var (missing upstream sync with css-validator)

I'm guessing this is an issue with https://github.com/w3c/css-validator

Incorrect validation of css calc in combination with var (missing upstream sync with css-validator)

Looking at the diff https://github.com/w3c/css-validator/compare/validator-nu i'm not sure if there is anything critical that is needed if the submodule pointed to the default branch

Accessibility gaps in the validator pages

I believe that link is to the legacy checker, rather than the "Nu" that is this repo https://validator.w3.org/nu/

Validator loses track of custom variables defined in separate <style> blocks

Likely needs to be raised on https://github.com/w3c/css-validator

Validator loses track of custom variables defined in separate <style> blocks

Actually, I think this is a duplicate of https://github.com/validator/validator/issues/1284, not related to the split styles

Support autocorrect on textarea

I don't think other "non-standard" attributes get added till they land upstream in the actual WHATWG/HTML spec