Re-initialize player after loaded, “Load more”/pagination buttons

  • Resolved thinkingcap5

    (@thinkingcap5)


    4 months, 1 week ago

    Hi,

    We are using the player on our Sermons landing page with a JetEngine listing. On load all works fine with the 9 sermons displayed, but when we click the “Load more” button to load more sermons, the play button no longer works on new sermons that are loaded.

    On pages where we make use of left and right pagination arrows e.g. https://joshgen.org/congregations/city-bowl/, the first and second sermons’ player buttons also do not want to play:

    Error:
    Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
    Element with focus: button
    Ancestor with aria-hidden:

    Can the JS be adapted to initialise the player after it has loaded?

    Thank you very much for any assistance. Love the player.

    ?…??

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter thinkingcap5

    (@thinkingcap5)

    I’ve had to roll-back to custom audio player on the links provided, but would still like to implement your player with pagination and load more buttons. We are still using the Castos SSP player on our sermons specific page https://joshgen.org/congregations/city-bowl/, where there is one player on the page, although the JetEngine listing uses a custom audio player where pagination and load more buttons are used.

    Please can you advise what changes can be made to re-initialize the player when load-more buttons are pressed, to ensure the play button works. I can created a test page to display the error, if needed.

    Thank you and kind regards

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    Hi @thinkingcap5,

    I believe the issue is that the JavaScript script initializing players on page load doesn’t “know” anything about players loaded dynamically via the “Load more” button.

    Unfortunately, I can’t advise a quick fix for this. Probably, you’ll need a developer’s assistance to dynamically initialize newly loaded players. You can review the assets/js/castos-player.js file and replicate the same logic in your own JavaScript.

    Best regards,
    Serhiy.

    Thread Starter thinkingcap5

    (@thinkingcap5)

    Hi Serhiy,

    Thank you for your reply, appreciate it.

    Kind regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Tags