Google Chrome seems to interfere with the navigation event of moving to the next page. The buttons are showing as enabled, but are acting as if not enabled. Is there an answer to this or do WebSoft need to address it?

Dear David,

please make sure that no other objects overlaps navi buttons (even with transparent parts!). Some browsers do not pass mouse events through overlapped transparent DIVs.

Could well be an issue with the xml or JS interpretation. Try a test page that uses a different object as a button.
Just use any page object and script a navigation event to fire on click.
If it works then the JS is probably OK and the error is the default button.
If so it might be worth making a custom template that uses a custom button set, you only need to make it once and save it as a template set to make it reusable.
Nick