Closed GoogleCodeExporter closed 8 years ago
I have the same problem.
I observe that this is happens when editor is executed inside a page received
by Ajax
request. This is somewhat connected with the process which jquery do after the
script.
Original comment by brusin...@gmail.com
on 22 Sep 2008 at 2:20
Anyone have a fix for this? I can't get it to work, AJAX rendered or not. Even
on a
static page, focus() doesn't seem to work.
Thanks!
Original comment by switch...@gmail.com
on 10 Nov 2008 at 6:10
I made to focus the document inside the iframe when focus event is dispatched at
Issue 20. But can be two things, the first one is that in FF it neves dispatch
focus
event because textarea is hidden. The other is that in FF you can focus the
document,
you will need to focus some other thing, like the iframe itself. I did not try
anything of this.
Original comment by joksnet
on 11 Nov 2008 at 9:30
This is a quick fix I am using for this issue.
The focus needs to be on the contentWindow.
Before line 439 (version 0.4) "$(this.original).focus(function()"
I added the following:
$(this.editor)[0].contentWindow.focus();
Original comment by spacover...@gmail.com
on 9 Jan 2009 at 7:24
Is there a fix for this ? can make it work with version 0.5
Thanks
Original comment by getconfu...@gmail.com
on 4 Feb 2009 at 3:57
Also using version 0.5 and noticing this problem. I'm using this with the ajax
form
plugin (jquery.form.js). If I dont use the ajax form plugin it works fine. Any
updates????
Original comment by jaw...@gmail.com
on 1 Mar 2009 at 8:20
I have a quick fix for this, if you use livequery
(http://docs.jquery.com/Plugins/livequery)
$("#id-of-text-area").livequery(function() {
$(this).wysiwyg();
$("#id-of-text-area").expire();
});
when the text area loaded, it will fire the function, and the use of expire()
eliminate the problem of multiple functions fired when load the text area
mutiple times.
hope this solve your problem.
Original comment by shx99...@gmail.com
on 9 Mar 2009 at 4:07
The quick fix of spacoverguy work great in FF3.0.7 with version 0.5 of jwysiwyg.
$("#frameId")[0].contentWindow.focus();
It gives the focus.
Cheers,
Mickael H.
Original comment by Mickael....@gmail.com
on 17 Mar 2009 at 11:36
Hello, I'm using: jwysiwyg v0.5, jquery v1.3.2
I have noticed the same problem, using FF 3.0.9. I'm applying the ().wysiwyg
function on all elements that have the same ID prefix or the same class, eg:
"#comm"
or ".a_txt". I've tried to apply some fixes posted above, but nothing changed.
Can
anyone post some feedback? Thank you.
Original comment by headless...@gmail.com
on 27 Apr 2009 at 10:12
Also having the same issue with ajax'd content with v0.5.
The contentWindow fixes don't work for me. :/ Suggestions would be greatly
appreciated.
Original comment by neko...@gmail.com
on 28 Apr 2009 at 6:06
Been trying to experiment more with this.
If you attempt to ajax content that contains a textarea as well as
$().wysiwyg() for
that textarea, the iframe is rendered, and if you print
$(iframeelement).contents().find('html').html() , the expected content is
there. But
all you get is white space underneath the toolbar where the document should be.
When you attach click event alerts on all elements within the iframe and the
parent
document, if you click on that white space, no event is registered.
Also, if you attempt to right click a wysiwyg that works, you don't get the
option to
view frame contents. But you do with a broken one and the frame source usually
contains an empty <html><body></body></html>.
I hope this helps someone with debugging because I'm no closer to trying to
work out
where the editor vanishes to when it breaks.
Original comment by neko...@gmail.com
on 29 Apr 2009 at 4:08
Nevermind my last two comments, found resolution in
http://code.google.com/p/jwysiwyg/issues/detail?id=54
Original comment by neko...@gmail.com
on 29 Apr 2009 at 4:36
Original comment by akzhan.a...@gmail.com
on 18 Dec 2009 at 2:18
Original issue reported on code.google.com by
sxlf...@gmail.com
on 17 Sep 2008 at 9:37Attachments: