User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:184.108.40.206) Gecko/20070515 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:18.104.22.168) Gecko/20070515 Firefox/22.214.171.124 I had to copy and paste this adress to VLC. I have tried to configure in Mozila Firefox VLC as client and have not found the way. Reproducible: Always Steps to Reproduce: 1.go to http://www.elmundo.es/servicios/retransmisiones/canalparlamentario/ 2. Click on VLC link 3.
I can see that using windows media player plugin. Try this: http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx
i think that the problem is that vlc plugin does not associate to mmsh protocol handling
Thanks, I used WMP plugin, but is much better watching it with VLC. The question is that there are no way, at least with the main menu to asociate to VLC the pages that begins with mmsh as mmsh://reflector.elmundo.es:9001/ I have found this protocol with VLC very good, and not as good with WMP (some cut) and I used it to listen spanish congress, leting a TV box, and listening as a radio broadcast most of the time.
updating title, i still don't know if this should be a firefox (NEW) or a vlc bug (INVALID), leaving UNCONFIRMED for further investigation.
Severity: normal → minor
Component: Extension Compatibility → General
Summary: unable to watch it or asociate with VLC → unable to associate mmsh:// protocol with VLC plugin
Adding dmose to get his opinion on this. This might be the sort of thing his new content handling work will address. If so, I can write a test case for this protocol and we can dupe this against one of the more general "provide support for arbitrary protocol" set of bugs.
The Firefox 3 content-handling work is unrelated to this; as it really just effects remote apps. Plugins, in general, are mostly about supporting stuff like (e.g.) the <embed> and <img> tags. I don't know whether or not it's possible to implement a protocol handler support in a plugin. If not, the VLC client application should be registering itself with windows as being the default mmsh: handler. Either way, this should be addressable by the VLC developers in current (all?) existing versions of Firefox.
Sometimes browser ask for a associate app because the extension of the archive you are downloading. Why not asking for any other application if the "prefix" is unsupported?. PS: I have reported this bug to VLC too with this link
please see also Bug 387675, i think it could be a similar problem
Status: UNCONFIRMED → NEW
Ever confirmed: true
If the application registered mmsh as a "URL Protocol" in the windows registry then we would support it. Any protocol we don't handle internally we hand off to the OS to handle.
This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days. http://tiny.cc/forgottennewbugs If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.
You need to log in before you can comment on or make changes to this bug.