Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-30217

Flowplayer controls are broken for audio content over https in Chrome and IE

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Minor Minor
    • None
    • 2.1.2
    • Filters, Resource
    • PostgreSQL
    • MOODLE_21_STABLE
    • Hide

      Not really a workaround, but I have tested https audio URLs with a custom JWplayer-based filter, works fine for the same audio in all browsers.

      Show
      Not really a workaround, but I have tested https audio URLs with a custom JWplayer-based filter, works fine for the same audio in all browsers.

      There seem to be a very specific bug in the current version of flowplayer audio plugin. Upon attempt to play the file over https in Chrome or IE, the player controls become broken in a way that clip duration is not shown, navigation slider is not functioning and pause button does not work. This is only applicable to audio content (handled by flowplayer plugin /lib/flowplayer/flowplayer.audio-3.2.2.swf), the video content accessible over https link works fine.

      This is the case for both File resource and media-plugin filter, as they both use the same M.util.add_audio_player method for initiating the player.

      The issue appears in Chrome 15.0.874.106 and IE 8, works fine with Iceweasel 7.0.1 and FF 8.0.

      To replicate, if your site is hosted via https, create a file resource to any mp3 file and observe the issue. Alternatively you may add a link to audio file hosted remotely over https to the Page resource.

      There seem to be a related bug already reported upstream, but the suggested fix does not solve the problem.

            rwijaya Rossiani Wijaya
            kabalin Ruslan Kabalin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.