|
|
Posted by shimmyshack on 06/29/07 16:29
On Jun 29, 2:28 pm, Joey33 <konrad...@gmail.com> wrote:
> Hello,
>
> Yeah, you're right. It works as you presented.
> I put the problem too simple. In fact, in my site it is as follows:
>
> page 1
>
> Iframe generated by JS with wysiwyg editor. Iframe dynamically
> replaces a textarea. It allows inserting images (with all necessary
> attributes of course). When submitted, JS recontsructs the body node
> making it xhtml compliant and places the contents of the iframe into
> the textarea. The form is sent to page 2
>
> page 2
>
> Again the same Iframe is generated this time however not editable.
> Images have onClick event allowing uploading images to server. In FF
> when the iframe has designMode=on they cannot be clicked. Anyway, the
> contents of the textarea from page 1 is inserted into the iframe and
> displayed. At the same time it is inserted into $_SESSION array. When
> the user goes back to editing mode, THE key in $_SESSION is empty.
>
> I agree that it should have nothing to do with browsers since it is a
> matter of server serving parsed pages. But, believe me, it is like
> that.
>
> When on page 1 I don't insert src attribute everything is fine. Maybe
> the JS function regenerating the body node messes things up. I'm
> trying to implement WYZZ wysiwwyg editor. If you feel like looking
> into the code:
> // WYZZ Copyright (c) 2007 The Mouse Whisperer
> // Contains code Copyright (c) 2006 openWebWare.com
> // This copyright notice MUST stay intact for use.
> //
> // An open source WYSIWYG editor for use in web based applications.
> // For full source code and docs, visithttp://www.wyzz.info
> //
> // This library is free software; you can redistribute it and/or
> modify
> // it under the terms of the GNU Lesser General Public License as
> published
> // by the Free Software Foundation; either version 2.1 of the License,
> or
> // (at your option) any later version.
>
> I went round this problem inserting src attribute at a later stage and
> it works.
>
> Thanks for your interest and help!
> Regards,
> Joey_33
my advice is to use a proxy to watch the data being submitted, if you
were using XHR I woudl suggest you use firebug, but as you are using
iframes a proxy will be more help. You will as you have suggest
probably find its a javascript problem, you might find that posting
pure html is a problem for some spplication firewalls (post payload s
which contain tags might be seen as injection attempts), have you
considered using a javascript parser that takes the attribtues and
uses json notation - with not tags, you can then use php's inbuilt
jason parser the otherside to recreate the original code.
Navigation:
[Reply to this message]
|