Closed Bug 141840 Opened 23 years ago Closed 23 years ago

Flash and Shockwave don't work in Mozilla 1.0 RC1

Categories

(Plugins Graveyard :: Shockwave (Adobe), defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mozilladev, Assigned: rubydoo123)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 I'm having a devil of a time getting Flash and Shockwave plug-ins to work in Mozilla. It seems this should work out of the box (most people will want to support this). Reproducible: Always Steps to Reproduce: 1. Download and install Mozilla 1.0 RC1 (clean install) 2. Navigate to www.maserati.com 3. Choose the English site 4. A new window will load and the Flash plug-in "Get the plug-in" dialog will appear. 5. Click on the "get the plug-in" to follow the link and download the plug-in for Netscape. 6. Run Flash installer. 7. Return to maserati site -- Flash still doesn't work. Actual Results: Flash plug-in doesn't work Expected Results: Flash plug-in should work immediately after install. If that can't work then Flash should at least work after download/install from the Flash site.
Have you entered "about:plugins" in url bar in order to say to mozilla there is a new plugin ?
You must manually copy the flash plugin into mozilla plugin directory or download flash6 which supports mozilla. -> b-g
Assignee: sgehani → Matti
Component: XP Apps → Browser-General
QA Contact: paw → imajes-qa
I realize a workaround for this might be possible, however I'm suggesting that Flash and Shockwave should work as soon as Mozilla 1.0 is installed.
This is a workaround for Macromedia installer that doesn't support mozilla. Use flash6 (supports mozilla) or copy it. That's no workaround for a mozilla bug. BTW: Mozilla scnas in the NS4.7x plugin directory (if installed)
--> plugins
Assignee: Matti → beppe
Component: Browser-General → Plug-ins
QA Contact: imajes-qa → shrir
won't 133282 take care of this?
133282 has been marked fixed, and with today's nightly builds, flash still does not work by default with a complete install. anthonyd
Depends on: 133282
um...bug 133282 won't effect Flash or Shockwave in any way because they do not install to a global, common folder as do those other plugins. :( Maybe they should.... However, the XPI for Flash, if delivered correctly from Netscape.com's Plugin Finder Service, should be small to download and install correctly for your browser. Another solution is to have Nav 4.x installed.
No longer depends on: 133282
right, also just re-installing flash and shockwave work as well. but again, it sounds like the what the reporter is saying is that they should work from the get-go. anthonyd
ok, here is the deal (i think) (beth, peter, please feel free to correct): with the commercial build, we DO install flash and shockwave WITH the installation of the browser. In my testing, both of them seem to work 'right out of the box'. with the mozilla build, we do not install shock or flash by default (do not know why). BUT, if you have a previous netscape install (where you HAVE installed shock and flash) pages that utilize the plugins will still work, as they are found and used. if you do not have a previous install before installing mozilla, then you will have to download and install the plugins. for me, when testing this way, everything worked fine. now my question is, what is this bug report for? Is it for: A) plugins are not installed by default with mozilla. B) plugins are not working after I have installed them (via default plugin, or manual install). C) plugins are not being found/used from my previous install. D) other (please specify). E) all of the above. just want to be clear, cause I dont get it. thanks, anthonyd
flash will work with the new pfs changes that greggl is about to put on netscape.com. users will download the plugin , if it is missing, fom the new pfs service and it will be painless..like the ipix plugin download.
A) plugins are not installed by default with mozilla.
Since Flash does not unpack the np*.* files automatically on install, there is not much mozilla can do after the fact. Flash would need to have those files accessible for us to scan. Until Flash provides an installer that does indeed do that, the user will have to go through either 1. a reinstallation of the plug-in, or 2. access the np*.* files from somewhere else. So, how should this bug be marked?
invalid. this affects mozilla only..and is a known fact to everyone who uses mozilla that this is a DIY kind of browser.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Component: Plug-ins → Shockwave (Adobe)
Product: Core → Plugins
QA Contact: shrir → adobe-shockwave
Version: Trunk → unspecified
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.