Closed Bug 211218 Opened 22 years ago Closed 22 years ago

Javscript to flash communication and vice versa does not work under linux

Categories

(Core :: XPConnect, defect)

x86
Linux
defect
Not set
major

Tracking

()

VERIFIED INVALID

People

(Reporter: mailsp, Assigned: dbradley)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 The Macromedia-examples for Javascript-Flash-communication do not work with Mozilla 1.4 (stable) under linux (other Javascript-to-Flash-comms that i tried do not work either) The examples do work under windows with Mozilla 1.4 (stable). Mozilla 1.3 does work, Firebird 0.6 does work too. Reproducible: Always Steps to Reproduce: 1. Go to the website metioned above 2. Go to "JavaScript to Flash communication" example 1 3. As written in the example: enter text into html-field, click outside, press tab Actual Results: The flash film does not display the text from the html-field Expected Results: The text should have been displayed in the html-field via JavaScript-to-Flash-Communication. I think it's a major bug, as many sites depend upon this feature and it worked in 1.3 (i checked this again today).
This bug is invalid, because it is a known bug, as it is written in release notes, "New Issues" : "If you're using the Linux GCC 3.2 binaries compiled by mozilla.org then JavaScript access to Flash will not work." http://www.mozilla.org/releases/mozilla1.4/README.html#new-issues Read the release notes before posting a bug, thanks ;-} Closing bug as invalid. Please reopen it if I am wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Verified. The "bug" is that the GCC ABI has changed from version 2 to version 3, and the JS-to-Flash code in Flash needs to have the browser using the same ABI. Which means you need a version of the Flash plugin built with GCC 3.x.
Status: RESOLVED → VERIFIED
Works with Flash Player 7.0r25.
You need to log in before you can comment on or make changes to this bug.