After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 314370 - plugin should only handle embedded media
plugin should only handle embedded media
Status: RESOLVED OBSOLETE
Product: totem
Classification: Core
Component: Browser plugin (obsolete)
unspecified
Other All
: Normal normal
: ---
Assigned To: totem-browser-maint
totem-browser-maint
: 354952 370619 443502 (view as bug list)
Depends on:
Blocks: 300691 301913 332550 334664
 
 
Reported: 2005-08-24 10:58 UTC by Jeff Waugh
Modified: 2014-04-30 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Jeff Waugh 2005-08-24 10:58:21 UTC
Please describe the problem:
The Totem plugin correctly handles embedded media objects, but also becomes the
default viewer for all the media types it supports. So when you click on a video
file, expecting a prompt to download or play (in the normal totem player), the
plugin takes over the entire browser display and plays the video. Most users
will expect file links to download or play in non-plugin totem.

Bastien asked me to file this to remind him to fix the issue. :-)

(I love totem.)

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Bastien Nocera 2005-08-24 13:39:58 UTC
I think it should be enough to not create the plugin when the mode is NP_FULL in
the NP_New function, but I'm not quite sure what kind of error we're supposed to
push back, or whether we can avoid the browser calling this function at all in
case of mode != NP_EMBED.
Comment 2 Christian Persch 2005-12-24 14:39:30 UTC
The exact error code doesn't matter, gecko just checks for != NPERR_NO_ERROR.
However returning an error doesn't seem to work here, it still does not pass the URL to the ext handler.
Comment 3 Bastien Nocera 2006-01-09 11:54:30 UTC
The upstream BZ is at:
https://bugzilla.mozilla.org/show_bug.cgi?id=306867
Comment 4 Christian Persch 2006-01-14 19:54:43 UTC
By chance I've come across this pref: plugin.disable_full_page_plugin_for_types [http://lxr.mozilla.org/seamonkey/source/modules/plugin/base/src/nsPluginHostImpl.cpp#3729]; this may do what we want? However it's not clear how to do set that pref from the plugin and have it apply, since the plugin will already be loaded when we get there afaict.
Comment 5 Bastien Nocera 2006-09-10 11:10:23 UTC
*** Bug 354952 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2006-11-17 00:18:21 UTC
*** Bug 370619 has been marked as a duplicate of this bug. ***
Comment 7 Christian Persch 2006-11-18 19:47:10 UTC
How about we simply launch totem ourself in ::Init, and then return an error code so the plugin gets aborted?
Comment 8 Bastien Nocera 2006-11-19 02:01:11 UTC
(In reply to comment #7)
> How about we simply launch totem ourself in ::Init, and then return an error
> code so the plugin gets aborted?

That would be a good thing to do until the Mozilla bug is fixed. Problem is that we'd like to have this to popup a dialogue asking whether to save it (bug 300691), or launch Totem. Any other ways to do that? Force Mozilla opening the stream with a bogus mime-type?
Comment 9 Christian Persch 2006-11-19 13:04:31 UTC
I think in this case, saving could be done in totem itself (bug 350261) after it's launched.
Comment 10 Sebastien Bacher 2006-11-25 18:36:47 UTC
Ubuntu bug about that: https://launchpad.net/products/totem/+bug/72032
Comment 11 Bastien Nocera 2007-06-04 09:23:13 UTC
*** Bug 443502 has been marked as a duplicate of this bug. ***
Comment 12 Maxim Levitsky 2009-04-09 08:41:26 UTC
This still isn't fixed!

I have ubuntu 8.10


This very annoying bug.

Comment 13 Bastien Nocera 2009-04-09 09:46:07 UTC
(In reply to comment #12)
> This still isn't fixed!

That would be because it's still a bug in Mozilla. Read the bug before commenting about something we already knew.
Comment 14 Maxim Levitsky 2009-04-09 10:24:05 UTC
I did read the mozilla bug.

Anyway last activity on it goes back to 2007.

This bug, is another thing, I can live with, but this is annoying.
Comment 15 Bastien Nocera 2009-04-09 10:28:08 UTC
This bug is directly linked to the mozilla bug. Unless Mozilla fix their browser, we can't fix our usage of their APIs.
Comment 16 Maxim Levitsky 2009-04-09 11:16:54 UTC
Fine, lets bug them to fix this in this case...... :-)
Comment 17 Bastien Nocera 2010-04-08 16:46:35 UTC
See also https://bugs.webkit.org/show_bug.cgi?id=37278 for WebKit
and
https://wiki.mozilla.org/Talk:Plugins:PlatformIndependentNPAPI
for the discussion about the Pepper extensions
Comment 18 Bastien Nocera 2014-04-30 11:22:13 UTC
The browser plugin has been removed from Totem. See this post for more details:
http://www.hadess.net/2014/04/good-bye-totem-browser-plugin.html