310488 - Flash is unvisible when it is dynamically inserted into a page with designMode set to ON

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Andrei Mourzenkov]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

When creating and inserting OBJECT for flash with JavaScript when document's
designMode is ON, flash is not visible, although its HTML code is actually
inserted. The sutuation is the same when new innerHTML containg OBJECT code is
assigned to an element, like DIV. When designMode is OFF, flash is inserted and
displayed as expected.

Reproducible: Always

Steps to Reproduce:
1. Create new OBJECT element with "createElement()" JavaScript method.
2. Populate all necessary attributes (type, data, pluginspage, width, height,
etc.) of the OBJECT with "setAttribute()" JavaScript method.
3. Insert the OBJECT to a page with "appendChild()" or "insertBefore()"
JavaScript methods.
Actual Results:  
FLASH is not visible

Expected Results:  
display FLASH

Comment 1

[u63580]

Can we have a simple testcase?

Comment 2

[Andrei Mourzenkov]

Attachment: test case to repeat the bug

Comment 3

[u63580]

Just to check I understand this correctly, for the testcase:

-With designMode off, pressing the Add Flash button adds a blue animation in the
yellow Frame.

-With design mode on, nothing happens in the yellow frame when you press Add Flash.

Comment 4

[Andrei Mourzenkov]

(In reply to comment #3) 
You understand it correctly. With designMode off, pressing the Add Flash button 
adds a blue animation in the yellow Frame. With design mode on, nothing happens 
in the yellow frame when you press Add Flash, however new HTML code is actually 
added to the Frame code, which can be evident in TEXTAREA. 

Comment 5

[Marcin]

I confirm this BUG is there !

1. Create new OBJECT element with "createElement()" JavaScript method.
2. Populate all necessary attributes (type, data, pluginspage, width, height,
etc.) of the OBJECT with "setAttribute()" JavaScript method.
3. Insert the OBJECT to a page with "appendChild()" or "insertBefore()"

The CODE is added to the page but FLASH is not visible !!!!!!!!!!!!!!
Please do something with this.
Opera is working perfect, even IE is working ok !
This is very important for WYSIWYG editors !

Comment 6

[augustus.kling]

This bug is not limited to Flash content, it applies for any object tag used in design mode (contenteditable).
The object tags are not rendered in design mode, instead the alternate content is shown. The test case attached above does not use any alternate content and therefore nothing is rendered.

If you would insert
<object data="image.png">There should be an image.</object>
the text was shown instead of the image.
When one is using the same code outside a design mode element, the image will be shown.

I tested this on Firefox 3 on Ubuntu 8.04.

Comment 7

[Comsultia, Ltd.]

this bug is blocker to most of wysiwyg editors and is 4 years old!

Comment 8

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 9

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 10

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 11

[Dmitry Dedukhin]

The problem still exists in Firefox 4.0.1 and can be easily reproduced with attached example.

Comment 12

[h_brena]

This problem can still be reproduced in FF 6 on Windows 7. It limits seriously the development of WYSIWYG editors.

Comment 13

[Samuel Cole]

This problem can be reproduced in Firefox 13.01, six years (and change) later. I've reduced it here: http://jsfiddle.net/samuelcole/6Te5C/2/

Comment 14

[Samuel Cole]

This problem can be reproduced in Firefox 13.01, six years (and change) later. I've reduced it here: http://jsfiddle.net/samuelcole/6Te5C/5/