Flash fscommand doesn't work if a Virtools object is in the same page



15 years ago
13 years ago


(Reporter: zyegfryed, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

In the page at http://mecagora.free.fr/bug/animation_ia1.htm, fscommand are not
Separately, the Flash and the Virtools object run correctly, but not in the same
page (It runs under Internet Explorer). It seems the presence of two plugins
stop the execution of fscommand...

Reproducible: Always
Steps to Reproduce:
1. Launch the webpage : http://mecagora.free.fr/bug/animation_ia1.htm
2. After Virtools and Flash (no preloader, please wait...) objects were loaded,
click on "Activer" button.

Actual Results:  
The Flash interface is just unfreeze.

Expected Results:  
The Flash interface is unfreeeze, a Virtools animation is launched (with a
camera transition), and the Flash interface is enabled.

Comment 1

15 years ago
More information : 
When you click on "Activer" button (Flash), it occurs 2 things in parallel :
- the blue "fog" over the interface disappear (set to invisible);
- a call to a fscommand is activated to start the Virtools animation, which 
when it finished, returns an action "to activate" the interface. 
With FireFox/Mozilla, it is this call to the fscommand which is not executed. 
So, the blue fog disappear (normal, it is only ActionScript), but animation is 
not started, and thus, a fortiori, the activation of the Flash interface.

So, when i say "the interface is unfrezeed", it means that the blue fog 
disappear. And when i say "the interface is enabled", it means that buttons can 
be clicked.
For french comments, take a look at this thread : 
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.