The content is not editable in firefox

[GoogleCodeExporter]

What steps will reproduce the problem?

Place the Textarea with Editor in an AJAX Content.
The Content was not showing and is not editable in firefox,
but it works in IE7.

Same Problem like this.
http://code.google.com/p/jwysiwyg/issues/detail?id=152

Original issue reported on code.google.com by johgep on 31 Mar 2010 at 2:47

[GoogleCodeExporter]

i have worked with jwysiwyg and textarea loaded from ajax, it works.

The response with ajax should be like:

<script>
$(function()
  {
      $('#test').wysiwyg();
  });
</script>
<textarea id="test"></textarea>

That's all, if you want to put your own content, just replace:

<textarea id="test">Content</textarea>

it work for me with ajax, if this isn't the problem, please, be more explicit.

Original comment by serg...@gmail.com on 31 Mar 2010 at 7:14

[GoogleCodeExporter]

no it does not work for me. i try it with IE7 and Google Chrome without 
problems.
But in Firefox I can't bring it to work. I don't see any problems in JavaScript 
Console.

You can test it by your self.
http://www.weinfreund.de/struts2-jquery-showcase-2.1.0-SNAPSHOT/index.action

Please go to "Effects\Interactions" > "Extend this Plugin" 

Original comment by johgep on 31 Mar 2010 at 11:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

you're right 

my navigator:

User agent : Mozilla/5.0 (X11; U; Linux x86_64; es-AR; rv:1.9.1.8) 
Gecko/20100214
Ubuntu/9.10 (karmic) Firefox/3.5.8

content is not editable

look this: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.execCommand]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
http://www.weinfreund.de/struts2-jquery-showcase-2.1.0-SNAPSHOT/index.action ::
anonymous :: line 975"  data: no]

this is a known mozilla FF bug, the way for solution is not to use execCommand
functions, this will require a lot of code and functions.

We talk about that

Original comment by serg...@gmail.com on 1 Apr 2010 at 6:32

Attachments:

• Pantallazo.png

[GoogleCodeExporter]

I should not use the execCommand function? 
Or the jwysiwyg plugin?

Original comment by johgep on 2 Apr 2010 at 7:54

[GoogleCodeExporter]

jwysiwyg uses execCommand function, but if you're using better dont do it.

Original comment by serg...@gmail.com on 2 Apr 2010 at 12:42

[GoogleCodeExporter]

This is the Mozilla bug. Editor fails when created while not visible yet.

It's easy to walk around it by call $().wysiwyg after showing the content with 
textarea 
(may be using setTimeout(createEditor, 0)).

Original comment by akzhan.a...@gmail.com on 2 Apr 2010 at 3:30

[GoogleCodeExporter]

Here is link to the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=433480

there is one right way - show AJAX content as is, and then (after) make call to 
wysiwyg.

Original comment by akzhan.a...@gmail.com on 2 Apr 2010 at 3:41

• Changed state: WontFix

[GoogleCodeExporter]

Issue 152 has been merged into this issue.

Original comment by akzhan.a...@gmail.com on 2 Apr 2010 at 3:41

[GoogleCodeExporter]

Simular issued on any other editor: http://dev.fckeditor.net/ticket/321

Original comment by akzhan.a...@gmail.com on 2 Apr 2010 at 3:43

[GoogleCodeExporter]

I change the code from 

$elem.wysiwyg(options.wysiwygoptions);

to 

$elem.wysiwyg(options.wysiwygoptions);
$(document).wysiwyg();

Bod the error in firefox still exists.

See:
http://www.weinfreund.de/struts2-jquery-showcase-2.1.0-SNAPSHOT/index.action

Please go to "Effects\Interactions" > "Extend this Plugin" 

Original comment by johgep on 5 Apr 2010 at 8:02

[GoogleCodeExporter]

with new version from today at github, it works also fine in firefox.

Original comment by johgep on 7 Apr 2010 at 7:51

[GoogleCodeExporter]

Thanks for the test.

Original comment by akzhan.a...@gmail.com on 8 Apr 2010 at 8:42

• Changed state: Fixed