fd://0 refers to stdin (the backend reads from the frontend through a pipe). It usually has to be done this way (rather than passing a URL) because firefox may have to pass cookies/authentication details/etc. to the website.
Though that brings up an interesting point here - could it be that the only URLs to have trouble might be mms: URLs? Because Mozilla obviously wouldn't know how to download them... something to investigate. Further info: nsPluginInstance::SetWindow is called three times, but after that - nothing. No call to nsPluginInstance::Write or nsPluginInstance::WriteReady. Which is also a suggestion that firefox wasn't able to send any data. One more thing about the apparent hang of the UI - if you test totem-mozilla-viewer by passing a video in over stdin, the UI doesn't seem to be updated until a sufficient amount of data to display video is shown. -- [dapper] playable movies can't be played if inside a web page! https://launchpad.net/bugs/38584 -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
