Re: HTML validator - A safeguard for old browsers is flagged up as an error

On 8 Jun 2015, at 15:21, Kelvin Warne wrote:

> When I insert an anchor in a page, I follow the advice in the w3 reference material

Which material are you referencing?

> and use eg. <a id="TopofPage" name="TopofPage"></a> to cater for old (name) as well as current (id) browsers. This is flagged as an error in your validators (both the original and your Nu Html checker).

The nu validator flags it as a warning, not an error. This is a feature that is required by the specification. (I believe the non-nu version just wraps the same engine for HTML 5, so I'd expect the same result there).

http://www.w3.org/TR/html5/obsolete.html#warnings-for-obsolete-but-conforming-features

> NB. A similar situation arises in the css checker when using the older IE Opacity style statement as well as the current one.

Do you mean `filter: opacity`? That has never been standard CSS. Happily, Microsoft have dropped support for it and implemented the standard.



-- 
David Dorward
http://dorward.co.uk/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQIcBAEBAgAGBQJVdayEAAoJEIx1Sul6qG3FP5oP/0kRFjTx4EvRc+7vpmoHO1+E
8dGT+btV0q7RtmK0afUxLn81h6uffJNnWB3MIh46dQyAySVi4Q0ZTKNSDxs10MzS
GZSnVag7wA66r20B1juksFCxS4fE4Bk4aUn7N8Bb3tAM1QkUxESQCHgnEtrIIuef
9A5bSsJGp7EB6L2BROrGU2ylDGzmpczcThb5ZE201ybs5zeDl4quFkCZyrs6SFtp
GYegwruiVfWqYlYJ9WQQPBd6xbtOYOJcInby6nPsXwkn9e67LE+IJbdDLjf9joik
3Ea8uwgRZ80Zyhax/wL5hzFDh2638hPVtkJgllkTBHyItbppxESeW0nhxSi2+aM1
pyyaPFJ2oFcWx9swhB1PdcGoi3bpsrkLxlDILIKm7OZ+SAL5j5NR8DWh1KkMUFr5
mhjjN8wkBYhLTHDkhSr9wH5OFu8/J9HTmbmmbEocBx4D9hSGUgCv2hysFSG2icnS
PGvU36+qwS4kMVUGJrcgF+aY53KhcKnl3Y3alw56F9qk6WxncsLh+yPFofiJ1rX/
oLScS1iI8Qf8pvS4dU9cJF2j72OLO4m1Otp82h6AlV1dDoCfWF9gnGngLMgGTlK3
js/HyXIPwmh6rDNC6ZSomZli5LdzMGe5aatHxVKLj3yxrc0kgANE51iAKxdt8Eib
KKzY1Wufj8inA3Iv4g9q
=5JRI
-----END PGP SIGNATURE-----