macromedia.com - FSCommands not working with OBJECT tags

RESOLVED INCOMPLETE

Status

Tech Evangelism Graveyard
English US
P2
normal
RESOLVED INCOMPLETE
15 years ago
2 years ago

People

(Reporter: Peter Lubczynski, Unassigned)

Tracking

({top100, top500})

Details

(Whiteboard: [PL2:NA][plugin], efu, URL)

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
You'll need Flash 6 with scriptability to test this bug. You can install the
version that comes with Netscape 7 by clicking here:
ftp://ftp.netscape.com/pub/netscape7/english/7.0/windows/win32/ewc9e/flash.xpi

This is from bug 183512. I'm having problems using FSCommands with the OBJECT
tag. Here are the two problems I am seeing:

1. Plugin does not seem to call into browser at all if the 'ID' attribute is
used instead of 'NAME'. If I add a 'NAME' attribute, at least I see the plugin
trying to call into the browser through GetURL.

2. If the call is made, the plugin uses the document.embeds[] array to attempt
to access its DOM node. However, this array only contains EMBED tags, not
OBJECTs, so the Javascript URL Flash uses to hook up 2-way scripting fails:

JavaScript error:
javascript: function jsScriptObject(obj) { this.wrappedJSObject = obj; }
jsScriptObject.prototype = { evaluate : function(expression) { return new
jsScriptObject(eval(expression)); } }; 
FAILS w/ OBJECT --->  var plugin = document.embeds['send_to_flash']; 
plugin.SetWindow(new jsScriptObject(window),1134180267); 
---->line 1: plugin has no properties



So I think Flash may need to be changed to use the more standards compliant
'getElementById' to access the DOM. However, we may be able to take a shot at
fixing this on our end. Here's the idea for the hack:

1. On OBJECT tags for Flash that have an ID attribute but not NAME, dynamically
copy the ID's value to a new NAME entry in the array of attributes/parameters we
pass the plugin in NPP_New.

2. We could add OBJECT tags tags to the document.embeds[] array such that the
script above would succeeded in getting the plugin. 
cc:ing jst for DOM impact on this change.
(Reporter)

Comment 1

15 years ago
Created attachment 108931 [details]
testcase

Comment 2

15 years ago
sooner rather than later
Priority: -- → P2
Whiteboard: [PL2:NA]
Target Milestone: --- → mozilla1.3beta

Comment 3

15 years ago
reassign
Assignee: beppe → peterl
(Reporter)

Comment 4

15 years ago
--->evang
Assignee: peterl → aruner
Component: Plug-ins → Plugins
Product: Browser → Tech Evangelism
QA Contact: shrir → mgalli
Target Milestone: mozilla1.3beta → ---
Version: Trunk → unspecified
(Reporter)

Comment 5

15 years ago
Created attachment 114118 [details] [diff] [review]
old patch (wip)

Comment 6

14 years ago
-> evang500
Keywords: evang500

Updated

14 years ago
Summary: FSCommands not working with OBJECT tags → macromedia.com - FSCommands not working with OBJECT tags
Whiteboard: [PL2:NA] → [PL2:NA][plugin]

Comment 7

14 years ago
SPAM: New Components
Assignee: aruner → english-us
Component: Plugins → English US
QA Contact: mgalli → english-us

Comment 8

14 years ago
Not sure what the status on this is, but in Moz 1.3, fscommands seemed to work
fine, but in 1.4 final, this error is coming up:

Error: plugin.SetWindow is not a function
Source File: javascript: function jsScriptObject(obj) { this.wrappedJSObject =
obj; } jsScriptObject.prototype = { evaluate : function(expression) { return new
jsScriptObject(eval(expression)); } }; var plugin = document.embeds['topnav'];
plugin.SetWindow(new jsScriptObject(window),2063466735);
Line: 1

Comment 9

13 years ago
This is still an issue with Shockwave Flash 7.0 r19
Keywords: top100

Updated

13 years ago
Keywords: top500
evang bug triage. Confirming bc's comment 9. Using FF 1.0 I get this in the JS
console: 
Error: window.document.get_var.SetVariable is not a function
Source File:
http://www.macromedia.com/support/flash/ts/documents/flash_to_flash_comm/flash_to_flash.htm
Line: 13

Marking for f/u
Whiteboard: [PL2:NA][plugin] → [PL2:NA][plugin], efu

Comment 11

7 years ago
INCOMPLETE due to lack of activity since the end of 2009.

If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself.

Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.