You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't test exhaustively, but I ran a few HTML files with intentionally-broken CSS through Nu, and it caught them. But Nu doesn't offer all the same options, as far as I can tell - you can't validate against CSS 2.1, for example, which is what we are supposed to do unless we know CSS3 will be okay (e.g., drop-caps). So it could be using CSS separately is the proper choice for now.
Is this issue about bundling the Nu validator or a different validator with the app?
If so, IMO we should either not do that, and instead point users to the online validator, or at minimum move this to
future featureNew feature or request, but not core
instead of
core featureRequired for basic PPing
.
Is this necessary, or is it now covered by the Nu HTML checker?
The text was updated successfully, but these errors were encountered: