Closed
Bug 219471
Opened 22 years ago
Closed 18 years ago
Problem when calling "SetVariable" Method from an embeded flash component
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: f.guillaud, Assigned: peterlubczynski-bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
After getting an flash-object reference within document, I can't call the
SetVariable method :
var mapObject = IE ? document.all("map") : document["map"];
if (mapObject)
{
mapObject.SetVariable("ids", id);
mapObject.SetVariable("enlarge", "1");
mapObject.TCallLabel("/", "loadPois");
}
The mapObject is found, but Mozilla says :
Error: mapObject.SetVariable is not a function
This was working with Mozilla 1.4 branch
Reproducible: Always
Steps to Reproduce:
1. Create an HTML with the following code :
<html>
<head>
</head>
<script language="javascript">
function run_test()
{
mapObject=document["map"];
if (!mapObject)
{
alert("No Object found");
return;
}
try
{
mapObject.SetVariable("fake", 0);
}
catch (err)
{
alert ("Error SetVariable :"+err);
}
}
</script>
<body>
<p>This is a flash plug-in interaction Test</p>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0"
quality="high" bgcolor="#FFFFFF" width="600" height="450" ID="map">
<param name="movie" value="http://www.mappy.com/x/demo.swf"/>
<param name="menu" value="false"/>
<embed NAME="map" type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"
menu="false" width="600" height="450" src="http://www.mappy.com/x/demo.swf"
swLiveConnect="true" quality="high" bgcolor="#FFFFFF"></embed>
</object>
<p>
<input type="button" onclick="run_test()" value="Hit Me !"/>
<p>
</body>
</html>
2. Load the page in Mozilla 1.5x, wait for the flash film to be loaded
3. Hit the "Hit Me" Button
Actual Results:
Mozilla reports :
Error: mapObject.SetVariable is not a function
Expected Results:
No error, communicate with Flash plugin and pass it the value
The flash plugin is an ActiveX object. Maybe this could be related
Comment 1•22 years ago
|
||
> The flash plugin is an ActiveX object.
Not in Mozilla. Mozilla uses the <embed> in the code you pasted.
Over to plug-ins.
I've been seeing a bunch of bugs on win32 recently that hint at some sort of
binary-compay problems with plug-ins (like this bug). Any idea what may have
changed since 1.4 in the way we build on Windows?
Assignee: dom_bugs → peterlubczynski-bugs
Component: DOM Other → Plug-ins
QA Contact: ian → bmartin
| Reporter | ||
Comment 3•22 years ago
|
||
Well, The bug as gone away by installing the last macromedia plugin version
7,0,14,0.
The problem arise for me when upgrading from 1.4 to 1.5
Maybe I can try some combinations of updates/fresh-installs if it may help.
Comment 4•22 years ago
|
||
Bug 221461 looks like a duplicate.
Comment 5•21 years ago
|
||
I have encountered the same bug under Firefox 0.9, and Shockwave Flash 6.0 r65
Comment 6•21 years ago
|
||
on another windows xp machine, firebird 0.7 exhibits the bug with flash 7.0 r19
Comment 7•20 years ago
|
||
When you upgraded to the new version, did you install into a different
directory, or delete the old directory before installing?
If so, I think this is a dupe of (or depends on) bug 233533, since bug 233533.
Read that over and see if it sounds familiar.
Comment 8•20 years ago
|
||
I just wanted to let you know that this doesn't seem to be a problem with Flash
Player 8 beta. If you do the install thing into a seporate directory, it doesn't
copy the flashplayer.xpt file over, but fscommand and flash scripting still work
anyway.
Comment 9•18 years ago
|
||
gone with newer version flash per comment 8, so closing invalid
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•