112684 - Macromedia needs to update Flash to be scriptable through XPConnect]

Status: VERIFIED DUPLICATE of bug 110441

(Tech Evangelism Graveyard :: English US, defect)

Description

[blockcipher]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120
BuildID:    0.9.6

We're trying to get a Flash menu in one frame to talk with a Flash movie in a
second frame.  I've been trying to work with some examples, but nothing works in
Mozilla or NS6.x.  For background purposes, the communication can occur from
Flash to JavaScript or from JavaScript to Flash.  I'm having trouble with both
directions.  Part of the problem when having JavaScript talk to I believe deals
with the object tag, but I plan on researching this more before filing a bug. 
The Flash to Javascript, on the other hand, is what this bug will focus on,
though there may be a relation between the two.

Sorry for the long-windedness :-)

Reproducible: Always
Steps to Reproduce:
1. Unzip the test case to a directory on your computer.
2. Open the toolbar.html in a browser window.
3. Hold mouse over the article button.
4. When menu is open, click on the New button.

Actual Results:  Nothing happens.

Expected Results:  An alert box should appear.  This works in IE 5 and Netscape
4.79.

Test case will be attached shortly with an HTML page, flash movie, and the
original flash file (.fla).

Comment 1

[blockcipher]

Attachment: Test case with movie, fla, and html doc

Comment 2

[Peter Lubczynski]

I was just about to mark this INVALID but I think Evangelism is a better home.
The problem is with the Flash plugin. AFAIK, Macromedia, at this time, has
choosen not to make Flash scriptable with Mozilla. Arun may have more details....

Comment 3

[blockcipher]

Thank you for clearing things up.  I had heard something to the same effect, but
I didn't trust the source, so I figured I'd submit a bug to be on the safe side.
 Hopefully Macromedia fixes this because I don't want to be stuck in a
one-browser world.  Please feel free to send me any other details you may have
on this subject.  Thanks.

Comment 4

[Bob Clary [:bc] (inactive)]

known issue, -> future

Comment 5

[Arun Ranganathan]

This one belongs with me -- I'm back from vacation :-)

Comment 6

[Arun Ranganathan]

[e-mail] and others,

I am engaged with Macromedia to try and get them to repair this issue, and am
cc'ing someone from Macromedia for further comments.
As you know, in the past plugins would expose themselves to scriptability via
the JRI/JNI Bridge via Java.  So plugin vendors who wished to expose methods
within their plugin to JavaScript would also supply a Java class file.
But we no longer have that Java-centric view of the world.  Going forward, we
want plugin vendors to implement their plugins using this resource as a guide:
http://mozilla.org/projects/plugins/scripting-plugins.html
As you can see, this prescribes some changes to be added on top of the standard
Communicator 4.x Plugin API:
http://developer.netscape.com/docs/manuals/communicator/plugin/index.htm

Comment 7

[Arun Ranganathan]

cc'ing kiwi :-)

Comment 8

[Bob Clary [:bc] (inactive)]

->Plugins

Comment 9

[Jonathan Watt [:jwatt]]

Does anyone know of any progress on this one? Kiwi would you be able to give us
any information on the Macromedia side of things? 

Comment 10

[Christian :Biesinger (don't email me, ping me on IRC)]

isn't this a duplicate of bug 110441?

Comment 11

[Peter Lubczynski]

Yes.

*** This bug has been marked as a duplicate of 110441 ***

Comment 12

[Kai Lahmann (is there, where MNG is)]

v

Comment 13

[Christian :Biesinger (don't email me, ping me on IRC)]

*** Bug 163441 has been marked as a duplicate of this bug. ***

Comment 14

[Nick Bebout]

SPAM: New Components