Forum Discussion

LimChinHong-f19's avatar
LimChinHong-f19
Community Member
5 years ago

Published Issue for Chrome and Microsoft Edge. HELP!

Hi, few month ago I done a SL project for my client, but today the client requested a little changing (add new VO and content). After revised it, I review in SL and everything work fine. Then I publ...
storyline 360
LeslieMcKerchie's avatar
LeslieMcKerchie
Staff
5 years ago

Hi Dan,

I appreciate you reaching out and sharing your findings and the Chromium bug that you tracked down.

Our team dug in a bit and it looks like Google may be correcting this issue in an August 3rd update. 

  • DanParker-ceba7's avatar
    DanParker-ceba7
    Community Member
    5 years ago

    Thanks Leslie! You are correct, while Google is increasing the limit of the WebMediaPlayer in an update next week, however, this will most likely not be the long term solution.

    The WebMediaPlayer limit is being raised to 1000 only until Chromium determines the final limit and communicates it out. I suggest that Articulate might want to be proactive in finding out a solution, or workaround, to cut down on the number of concurrent WebMediaPlayer instances before Chromium cuts the limit down again. Otherwise, some of us will be left with broken or unplayable media again in a few months time and will be scrambling to find a solution.