Invalid "self-closing element not allowed" JavaDoc error
roger.riggs at oracle.com
Fri Jul 26 13:44:34 UTC 2013
The html subset that appears in javadoc comments does not exist in isolation
or in a full browser context.
It is deliberately limited and structured to work within a documentation
defined by javadoc and supported by the javadoc stylesheet using HTML 4.01.
Html provided by the developer conforming to javadoc conventions can be
assured of a robust and consistent presentation.
Other tools besides browsers consume the generated html and those tools
should have a clean definition of the input they rely on. This
that provide javadoc, conversions to more structured documentation such as
on-line help and localization.
On 7/26/2013 9:23 AM, Stephen Colebourne wrote:
> On 26 July 2013 13:58, David M. Lloyd <david.lloyd at redhat.com> wrote:
>> On 07/26/2013 04:39 AM, Stephen Colebourne wrote:
>>> Its websites and
>>> browsers that define what should be accepted as HTML, not standards.
>> This is the craziest thing I've read all week.
> What percentage of the worlds websites contain valid HTML/XHTML
> according to the DOCTYPE/validator?
> I'd be amazed if its more than 1%.
> The Oracle home page, java.net, java.com and J2SE download page all
> fail validation. Yet all are perfactly usable websites.
> Tim Berners Lee said in the linked article: "Some things are clearer
> with hindsight of several years. It is necessary to evolve HTML
> incrementally. The attempt to get the world to switch to XML,
> including quotes around attribute values and slashes in empty tags and
> namespaces all at once didn't work".
> This isn't Java EE. HTML is a space where standards are a *guide*. I
> absolutely stand by my statement.
More information about the core-libs-dev