I found through some dodgy JS code of my own that multiple calls of scPlayer() on a source element weren't being aborted if the scPlayer() functionality was already applied. This resulted in the internal links of the generated scPlayer() element (such as #play, #pause, #info, etc.) to then try to be referenced as scApiUrl()s which then resulted in errors and no media being loaded.
I think ideally all the var setting logic which involves DOM-crawling would follow the abort code so as to lower any further unnecessary overheads.
I found through some dodgy JS code of my own that multiple calls of
scPlayer()on a source element weren't being aborted if thescPlayer()functionality was already applied. This resulted in the internal links of the generatedscPlayer()element (such as#play,#pause,#info, etc.) to then try to be referenced asscApiUrl()s which then resulted in errors and no media being loaded.I think ideally all the var setting logic which involves DOM-crawling would follow the abort code so as to lower any further unnecessary overheads.