Does the Glossary popup/tooltip etc work when publishing to HTML5?

[FrameMaker-dk]

I am publishing a book to HTML5. The text contains words which I want to have in glossary. I should be able to get a tooltip/popup etc on the glossary terms, but that does not happen in the published HTML5. The markup looks right - I do have the terms/definitions included in the glossary, but no visible indicator. 

I have used all three skins with the same lack of results.

So... does the feature work? If it works - how?

FrameMaker  Version: 17.0.7.842

[Jeff_Coatsworth]

Got me. According to this - https://help.adobe.com/en_US/framemaker/using/index.html#t=using-framemaker%2Fuser-guide%2Ffrm_books... - you use 2 different types of markers.

Both Rick & Barb have entries about glossaries, but they're a bit out of date for v2022 and seem to talk mostly about print glossaries. See https://www.rockymountaintraining.com/adobe-framemaker-creating-a-simple-glossary-for-a-book/ and https://techcommtools.com/by-request-framemaker-glossary-and-glossaryterm-markers/ 

[FrameMaker-dk]

Thank you @Jeff_Coatsworth Yes, working with glossaries in print works fine. What perplexes me, are the options for having a tool tip or a hyperlink showing in the html5 version. I can't seem to make that feature work.

[Jeff_Coatsworth]

I can get a glossary tab created in my HTML5 output, but that's only due to importing the FM content into a RoboHelp project and generating the HTML5 from there. Even then, it doesn't appear as a pop-up on the terms in the text, but a separate function tab with drop-downs for the definitions.

[FrameMaker-dk]

The glossary tab is a built-in feature in the skins, that comes with FrameMaker. Glossary words will appear correctly in that tab.

[Jeff_Coatsworth]

Ah, so that part is working? Just not the pop-ups on the terms in the topic text?

[FrameMaker-dk]

Yes, I can generate a glossary as a LOF and I can have the glossary added to the tab in HTML5.

BUT I should be able to have a tooltip/popup etc on the gloassary terms in the HTML5. And that feature does not work for me.