6.83 KB, application/x-zip-compressed
Created attachment 175810 [details] Simple test-case, contains HTML page, and a Flash movie along with the FLA source
We search for plugins already installed on the system and use them if they're there; so if you have flash for Netscape 4 or something installed, we'll pick that up. That doesn't pick up xpt files, however, as you noticed. For that you actually need to install Flash for use with Firefox/Mozilla... The default Mozilla install doesn't contain Flash itself (as you can trivially check by just looking at the files it installs).
(In reply to comment #2) > We search for plugins already installed on the system and use them if they're > there; so if you have flash for Netscape 4 or something installed, we'll pick > that up. That doesn't pick up xpt files, however, as you noticed. For that you > actually need to install Flash for use with Firefox/Mozilla... > The default Mozilla install doesn't contain Flash itself (as you can trivially > check by just looking at the files it installs). Okay, I have noticed that there are no flash plugin files, but I didn't know what flsah player it was using since it was installed into a new empty folder. However, the question is, why does it pick up a copy of flash plugin it finds on the system, when a full flash plugin installation is required in order for it to work properly?
In general, all installed plugins are picked up, on the assumption that if they're installed they're meant to be used. Most flash works just fine with just the plugin; some advanced features also require the xpt... In any case, this is not an installer issue.
Probably not, because I, for one, can't think of a reasonable way to "fix" this. Care to suggest one?
I already did in my first comment :-) Either pick the existing flash plugin from the system in such a way that it will function properly as it should, or, if this is not possible, do not pick the existing flash plugin with partial functionality at all. Since I'm mainly working with SQL and don't know how all this is working, I can't suggest any other solution. In this case, the solution is not so important to me - but the result is.
How, exactly, are we supposed to tell that it won't have full functionality? In fact, what is "full functionality"? Note that a number of users actually want the non-scriptable flash only, because it's less of a security risk.
This is the same as bug 233533 (which has been ignored for a long time now). I wonder how many other plugins loose functionality because an important part of the plugin is not copied during the first run. How does the flash plugin use the xpt file? Is there some way to initialize a plugin when it is copied to try to see if it is loading an xpt file? If so, that file could then be copied along with the plugin (from the same directory tree that the original plugin was copied). I'd say that if it does try to load an xpt file, and it is not available, the plugin should not be copied at all, and the user required to reinstall it manually. Since it is conceivable that this problem is not unique to flash, and could actually be a problem with future plugins, as well as possibly some older or more obscure plugins, I'd say that is deserves attention - even if that attention is simply a note about it in the plugin development docs. > Note that a number of users actually want > the non-scriptable flash only, because it's > less of a security risk. This is absolutely not a valid reason to not fix a bug. There may be a valid reason, or even a whole bunch, but this is not one of them. Finally, it looks like Macromedia has removed the need for the xpt file in Flash 8, since fscommand and flash scripting both work without this file. This is still a bug though, with more general possible future implications with regard to plugins in general.
if anything, is this an enhancement? And, would it not require adobe to deliver some change?
Not an enhancement. Unless there is some warning about using external support files in the plugin development docs, then this is a bug in the way that Mozilla searches for and copies installed plugins from other installed browsers - namely, when Mozilla copies the plugins, it does not copy all possible support files (like flashplayer.xpt). The fixes are: 1. Find some way to copy the external support files (maybe it isn't possible). 2. Don't search and copy plugins at all, if you can't be sure you are getting everything (which means you will have to manually install, or be prompted by Mozilla, and as a bonus, will get the most recent version of whatever plugin - a bonus in my book). 3. Add bright red blinking text to various places in the plugin development docs that warn plugin developers that their plugins may not function properly if they distribute and use external support files with their plugins.
if this, as you say, this the same as bug 233533, and bug 233533 is confirmed, doesn't it make sense to dupe this to bug 233533?
http://dev.neomyz.com/url_test.html WFM on Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20130621 Firefox/24.0 ID:20130621031051 CSet: 7ba8c86f1a56 It shows the URL and the version of Flash 11.7.700.202