Closed
Bug 35351
Opened 24 years ago
Closed 24 years ago
Shockwave PlugIn does not work when not wrapped under HTML
Categories
(Core :: Security, defect, P1)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: cleske, Assigned: jat)
References
()
Details
(Keywords: shockwave, Whiteboard: [nsbeta3+][nsbeta2-])
Attachments
(1 file)
3.91 KB,
text/plain
|
Details |
THIS APPLIES TO WIN95/98/2000/NT AND MacOS! After installing the Macromedia Shockwave PlugIn and surfing over to http://www.shockwave.com, none of the original Shockwave content is played (note: Shockwave Flash content is played back, but crashes the browser after some times). Here is the report that i got from Dan Sadowski, one of our senior developers: When the plugin is loaded, we are passed in a table of function pointers - actually known as "routine descriptors" on the mac. These are utility routines provided by the Netscape host environment. When we attempt to use one of these routines, such as NPN_MemFlushUPP or NPN_MemAllocUPP, Netscape crashes. The code to use these routine descriptors works fine in Netscape 3, Netscape 4 & Internet Explorer/Mac. You may contact him at dsadowski@macromedia.com or me at cleske@macromedia.com
Reporter | ||
Comment 2•24 years ago
|
||
Hi Shrir (or whatever your real name is), we don´t think that his problem is related to Javascript only, as we neither can drag and drop or open Shockwave Files alone in the browser wihtout any html page wrapped around. MOZILLA MUST LIVE! Greets, Christophe Leske
Reporter | ||
Comment 3•24 years ago
|
||
Hi Shrir (or whatever your real name is), we don´t think that his problem is related to Javascript only, as we neither can drag and drop or open Shockwave Files alone in the browser wihtout any html page wrapped around. MOZILLA MUST LIVE! Greets, Christophe Leske
Comment 4•24 years ago
|
||
cleske@macromedia.com - are you still seeing this problem with recent builds of Mozilla? Gerv
Keywords: shockwave
Updated•24 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 7•24 years ago
|
||
Hi, is nsbeta2 out yet?
Comment 8•24 years ago
|
||
nope..around june end..if i am not wrong.
Comment 10•24 years ago
|
||
*** Bug 36569 has been marked as a duplicate of this bug. ***
Comment 11•24 years ago
|
||
This page rely heavily on JavaScript, so we need to wait when old LiveConnect content is supported. As to not being able to open standalone files -- this is another issue: full page mode is not working yet.
Status: NEW → ASSIGNED
Comment 12•24 years ago
|
||
Since LiveConnect is not going to be working with old style plugins and full page mode has a separate bug, I see this one as a candidate to WONT FIX.
Comment 13•24 years ago
|
||
bug 39071 which has been marked as a duplicate of this bug does not launch any pdf files when used within a url. Should I reopen that one if it is a different issue that this?
Comment 14•24 years ago
|
||
No this is different. I believe this bug is about detecting plugins via JavaScript. My prev comment associating it with LiveConnect was wrong. This one is probably because of 37522. With my today changes 39071 should be fixed.
Comment 15•24 years ago
|
||
So what's the verdict here? Is this, in fact, the same issue as bug 39071? (And did your changes fix it?)
Comment 16•24 years ago
|
||
No this is not. This one is about JavaScript not being able to detect if the plugin is installed. Putting estimation date.
Whiteboard: [nsbeta2+] → [nsbeta2+] Est. 7/20
Comment 18•24 years ago
|
||
Moving from [nsbeta2+] to [nsbeta2-] per PDT PlugIns QA Beta2 Review.
Keywords: relnote2
Summary: Macromedia Shockwave PlugIn does not work for any SW content → Shockwave PlugIn does not work when not wrapped under HTML
Whiteboard: [nsbeta2+] Est. 7/20 → [nsbeta2-] Est. 7/20
Comment 19•24 years ago
|
||
Wrong assumption regarding dependency. Possible security issue, since saving the whole page source in a local file resolves the problem. Removing dependency.
No longer depends on: 37522
Comment 20•24 years ago
|
||
Comment 21•24 years ago
|
||
The attachment is HTML code which is identical to the Macromedia home page source, except I added base URL in the header to make all relative links work. If you open this file from a local drive the JS detection code works and the page displays the Flash content. That's why security is suspected. Reassigning to JavaScript.
Assignee: av → rogerl
Status: ASSIGNED → NEW
Component: Plug-ins → Javascript Engine
QA Contact: shrir → pschwartau
Updated•24 years ago
|
Assignee: rogerl → mstoltz
Component: Javascript Engine → Security: General
QA Contact: pschwartau → czhang
Comment 22•24 years ago
|
||
Reassigning to Security for triage or acceptance. Is this a Security issue, or Engine ?
Comment 23•24 years ago
|
||
Looking at it...
Status: NEW → ASSIGNED
Whiteboard: [nsbeta2-] Est. 7/20 → [nsbeta2-]
Target Milestone: --- → M19
Comment 24•24 years ago
|
||
Nominating for nsbeta3. Everyone, we need to get Shockwave working for nsbeta3 without fail.
Keywords: nsbeta3
Updated•24 years ago
|
Whiteboard: [nsbeta2-] → [nsbeta3+]
Comment 25•24 years ago
|
||
Escalating to nsbeta3+.
Updated•24 years ago
|
Assignee: mstoltz → jtaylor
Status: ASSIGNED → NEW
Comment 26•24 years ago
|
||
->jtaylor
Comment 27•24 years ago
|
||
cleske, would you please file a separate crash bug report on the URLs at which you're seeing crashes? I don't understand the relationship between Shockwave, Flash, and "Shockwave Flash" content--when "Shockwave Flash" content is being run, is it the Flash plugin or the Shockwave plug-in that's running at that time? Changing from P3 to P1 as we need to get Shockwave running ASAP during beta3 cycle so we can get some testing before releasing nsbeta3. John, is there any way we can fix this bug within the next week or so so that our plug-in partner Macromedia still has time to do further testing and find other bugs that may be exposed once this one is fixed?
Priority: P3 → P1
Comment 28•24 years ago
|
||
Adding Shrirang, who was doing plug-in QA last time I checked, to cc: list.
Assignee | ||
Comment 29•24 years ago
|
||
This bug is my top priority right now, I will get back with an ETA today.
Status: NEW → ASSIGNED
Assignee | ||
Comment 30•24 years ago
|
||
I can not reproduce with 8/21 commercial build on NT. What are the exact steps for reproduction?
Comment 31•24 years ago
|
||
Putting on [nsbeta2-] radar. Bug already set for [nsbeta3+], missed PR2 train :-(
Whiteboard: [nsbeta3+] → [nsbeta3+][nsbeta2-]
Comment 32•24 years ago
|
||
Peter Grandmaison <pgrandmaison@macromedia.com> is available to help with this bug if needed.
Comment 33•24 years ago
|
||
ohn, the URL is http://www.macromedia.com/ You should see no Flash content when you go to this page, which is a bug. There is also a link on the page saying something like 'If you know you have the plugin click here'. When you click you should see Flash playing. If you save attachment (2000-07-19) as an HTML file locally you will see Flash playing fine after you load it. The HTML code in the attachment is identical to that of www.macromedia.com
Assignee | ||
Comment 34•24 years ago
|
||
Unable to consistantly reproduce with recent builds. Marking WORKSFORME.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 35•24 years ago
|
||
Verified worksforme on Mac and Win98 branch 10/3 builds.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•