FM Table cross ref link works in published PDF, doesn't work in HTML5 (all other X-refs work)

[lookandlive]

I am somewhat new to publishing FM in HTML5. When I publish an FM book in PDF, all of the clickable cross ref links work properly. When I publish the same book in HTML5, all cross refs work except the Table cross refs. The character formatting of the Table link text is proper in the HTML5 (underlined/blue), but the link does not function. The table links are tied to (sourced from) the Structured Element = TableGroup (Cross Ref Source pod). All other cross ref link types work in the HTML5 (created from elements for figures, sections, steps, ...; links within the same file and links from file to file within the book).

The cross ref  Reference Format for the table and figure links are the same (<Xref>Figure\ <$elemparanumonly>; <Xref>Table\ <$elemparanumonly>).

The HTML Setup utility maps "Element = Figure" to HTML5 Division and "Element = Table" to HTML5 Division (same mapping, but different result)

I don't know if this is of importance: The element type in the HTML Setup Utility window is "Table." The element type that is used in the Cross Ref Source Pod when creating the link is "TableGroup." (different element names; the only option in Setup is "Table"; the only option for creating the link is "TableGroup")

Can anyone suggest what I can do or where I should look to learn how to fix the HTML5 Table links?

Thanks

FM2019, Structured, book with 6 files, MS Windows 10 Pro

[Matt-Tech Comm Tools]

Are you using the Publish panel, or modifying the reference page tables?

[lookandlive]

Thanks for your question.

I am using the publish panel to generate a PDF and then later for Responsive HTML5. 

I have viewed  the reference page info that FM auto generated when I published HTML5, but I have not modified anything in those auto generated Ref pages.

[Matt-Tech Comm Tools]

Excellent!

Using the Publish panel is the most advanced and controllable way to produce HTML.

The Reference pages were from circa 2000, prior to the Publish engine used now.

You mentioned that you are working with structured content in FrameMaker 2019...can you confirm that your content is structured?

If so, do your elements have paragraph formats (other than Body) applied to them?

[lookandlive]

Thanks for your replay and question.

Yes, most of our documents are structured. The document that I am having trouble with (no Table links in HTML5) is a structured document.

Yes, there are many paragraph formats. I think most element types use Body. The non-Body formats are mostly used for "title-like" paragraphs (at the beginning of a section - levels 1, 2, 3, 4 ...; unnumbered preface, numbered chapters and alphanumeric appendices, procedure titles, ...) or to make the text have a different appearnce (e.g. explanatory text = Body; software code = different paragraph format).

The paragraph format used with the Figure element is Body. The paragraph format used with the TableGroup element is also Body. 

[lookandlive]

Sorry. Should I wait and hope for an answer/suggestion?

[Matt-Tech Comm Tools]

Sorry I don't have a direct answer, but alas, I don't have direct experience with your issue.

I've not used the HTML Setup Utility, so I can't speak to that method of assigning conversion preferences. 

(I haven't used it yet, but will certainly be looking at it the next time I set up structure to convert to HTML)

With structured documents, I've assigned specific paragraph formats within the EDD, and then mapped the paragraph formats to the appropriate structures in the Publish options.

[lookandlive]

Thanks for your time and help