More often in practice such anchors get styled as links which isn't cool at all. Depends on the style sheet in use, of course.
This will be OUR stylesheet. I trust we can avoid such mistakes.
Suggested replacement:
<li><p><strong>Use the ISO-8859-1 aka. Latin-1 character encoding.</strong>
Why is this there, if I may ask? Why not use something like UTF8 instead? If I'm authoring a Mozilla.org page and need some non-English text on it (eg testcases for rendering or something), am I supposed to encode every single char as an entity?
I'm fine with us deciding the answer is "yes" as long as we have a clear rationale for it.
| Unfortunately, that tag makes 3.0-vintage Navigators load | the document twice and generally lose their minds.
Come on. That's an obsolete excuse.
This goes in the category of doing things you know will break browsers for no good reason other than "I can do it." We should not be doing such things, imo.
| Add meta description and keywords to help indexing.
What's the concrete use case that justifies this requirement?
The fact that we may want to write an indexing tool that does a better job of searching _documentation_ in particular than Google does. Google indexes a whole lot of non-documentation crap on the Mozilla.org site.
Google doesn't use such metadata because out in the wide world it is unreliable. On our own website, it will be reliable, since we control all of it.
-Boris
