This has little impact on the rendered page in the browsers i've seen it with, but i can't figure out _why_ Flare would do this. A similar topic i saw was viewtopic.php?f=12&t=17180 but that was about ordered lists, and recommended using a post-build javascript to strip the attributes (not sustainable for us)
We use a python script to parse a set of files and generate an unordered list of links to those, store the ul in an html file (externally to Flare project) and then bring the html file into Flare. All looks happy in the flare source, we have well-formed xhtml and Flare does not complain. However, when we build, the list items mysteriously have the value attribute applied to them.
Is this a known behavior? is there a switch somewhere that impacts this? it seems pretty unnecessary to me if it is known/configurable, but maybe it's Flare responding to some other error in the file?
any wise Flare heads who can explain this, please?
thanks
Owen