mangui / mangui/flashls

Videojs.swf related

Open
#497 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

fixed/answered notflashls/cantfix videoJS
Dominant language
ActionScript
Stars
744
Forks
259
PR merge metrics
No merged PRs in 30d

Description

Hello

I have been testing the hls.js from dailymotion and the videojs integration that you pointed out https://github.com/benjipott/videojs-hlsjs

I m pretty amazed by the result, especially on low end machine, it works fine where flash would freeze. Overall the behavior is great.
My only issue is about IE not being compatible.

I found a workaround by setting up 2 exact same source with different mime type ("video/mp4 used by your flashplayer and "applicaltion/x-mpegURL") and a tech order (hlsjs/flash) in videojs options.

That allow me to use your custom flashplayer as a fallback in case a visitor use IE, even if IE display a very dis-gracious warning when he attempt to load the first source.

But wouldnt it be better if the custom flashplayer was able to automatically take over hlsjs when IE is detected? I am not sure I was clear. basically I m thinking with a little tweaking of the actual scripts, it would be possible to use your videojs.swf as an automatic fallback and therefore allow a much wider browser range to be compatible.

Regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked videojs-hlsjs integration and the existing videojs.swf behavior first, with IE fallback handling as the focus. Done would mean the Flash player automatically takes over when hlsjs is not compatible, without requiring duplicate sources or producing the reported warning.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.