HTML5 Unordered List Bug

[GeorgeBell]

After many days of struggle, it appears we have found a bug in Flare's HTML5, when validated by the "Nu Validator" from W3C

Ordered Lists <ol> are no problem.

Unordered lists <ul> however result in the error, "Attribute "value" not allowed on element "li" at this point." (Bit of a shock when you have over 4,200 of this one)

[Brigit]

What exactly is the attribute that the validator objects to?

[GeorgeBell]

I wish I knew! However, it is a bug in Flare's export to HTML5, and only occurs with unordered lists. Madcap have confirmed this.

But far more alarming is a statement from Madcap yesterday which says, "Unfortunately, the upshot is that Flare 2013 r3 does not produce HTML5 output that validates with W3C."

Further comment from me at this point would not be acceptable!.

[Psider]

I think it's complaining about this (taken from Madcap's Flare help):

<ul>
<li value="1"><span class="SetOffFirstLevel">Getting Started Video </span>The Getting Started Video provides a visual demonstration of how to create a new project, introduces basic information about Flare, and points you to additional videos and resources to further develop the project.</li>
<li value="2"><span class="SetOffFirstLevel">Getting Started Guide </span>The Getting Started Guide is a PDF that explains how Flare works and introduces you to some of its key features and concepts. It then outlines the five basic steps for developing a project and producing output.</li>
<li value="3"><span class="SetOffFirstLevel">Getting Started Tutorial </span>The Getting Started Tutorial is a PDF file that you can use alongside Flare to create, develop, and generate output from an actual project.</li>
</ul>

The Mozilla site says "it has no meaning for unordered lists" (https://developer.mozilla.org/en-US/doc ... Element/li), which I would interpret as 'just ignore it', but I assume the W3C takes a harder line and defines it as only permitted for ordered lists.

[GeorgeBell]

It does indeed only apply to unordered lists, but would be possible for Flare's developers to deal with it.

However, when you are faced with a validation report which contains over 4,000 such messages - all flagged as an "Error", not a "Warning" - among a total of over 12,000 issues, one does get rather hacked off, to put it mildly.