TOPIC:

Hi

I'm currently using XOT 2.1 and have successfully created, exported and imported an LO as a SCORM package into Moodle 2.5, but I'm experiencing a couple of issues with the Glossary function.

The glossary pop-up window displays correctly if I preview the LO offline but does not display if I try to open it in the Moodle SCORM version. The pop-up appears but has no content.

Whilst the glossary links in the text do display, I keep getting double tooltips. One generated by the LO and the second by the browser. Is there any fix for this?

Hi Fiona,

Thank you for asking this as it's been one of the things that has bugged me for longer than I can remember, and i've just never found the time to fix it, until now...

I'm not sure what version you are on so i'll just outline the steps - i'm about to commit into the main code so in a future update it will be included so you have no worry about any of these changes being overwritten...

What you need to do (or ask your technical people to do) is locate the file at:

/modules/xerte/parent_templates/Nottingham/common_html5/js/xenith.js

Within that file there is a section dealing with glossary so do a search for this:

.on("mouseenter", ".x_glossary", function(e) {

The code should have something like:

Add in the two extra lines to make it

This will remove the title attribute on hover, which is what the browser uses and will stop the browser tooltip...

For compatibility with other things though it's probably best practice to replace it when we are done so now dow a search for:

.on("mouseleave", ".x_glossary", function(e) {

and change this code

to this

Save the file and refresh your Learning Object (You may have to clear your cache). There should now only be one tooltip... I don't want to actually send you a file as I have no way to know what version you are on but if you locate the file in your distribution and cannot manage to do this then please attach it and i'll patch it and get it back to you...

John

I meant to say that I don't know what the SCORM issue is but we can certainly investigate it for you. Are you able to attach some screenshots of the actual problem showing itself and of the development console showing any errors?

To open the console you press Command - Option - J (Mac) or Control -Shift -J (Windows/Linux)

John

By heart (I am not behand my system) there is a better fix in the xenith.js of the editor branch where I don't create the title attribute at all. But I need to check that.

I thought of doing that but i'm not 100% sure how that sits with screen readers and accessibility...

Good point. So let's ask Alistair.