taoguan / jwysiwyg

Automatically exported from code.google.com/p/jwysiwyg
0 stars 0 forks source link

tags are not displaying on html output #73

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Add some text along with the tags in the textarea.
   ex:<name>Sumanth</name>
       Hello how ru   
    i saved the abve content and tried to the open the it 
    using the editor.
2.
3.

What is the expected output? What do you see instead?
Editor should display the output with the tags, but it just showing 
'Sumanth
 Hello how ru'. Its not showing the tags

What version of the product are you using? On what operating system?
i am using jquery.wysiwyg.pack.js and jquery-1.3.min.js under linux.

Please provide any additional information below.

Even if i am trying to write some xml content in the editor, it's not
displaying the output with xml tags.

Original issue reported on code.google.com by sumanth....@gmail.com on 20 Jan 2009 at 6:51

GoogleCodeExporter commented 8 years ago
tags are not encoding properly after saving.let me explain this with one 
example.
ex:<test> tag converts into '<test>' by the editor, 
    but ideally editor should convert the code into &<test&>, that way
editor will load the tag as <test>

Original comment by sumanth....@gmail.com on 28 Jan 2009 at 2:06

GoogleCodeExporter commented 8 years ago
I've been experimenting with this today after running into it myself:

* "<xxxx yy zz" - no closing ">" - shows as "yy zz".
* "< xxxx yy zz" - with space after "<" and no closing ">" - shows correctly.
* "x<*>y" - where * is any string, even including whitespace - shows as "xy".

Original comment by chad+goog@sapphirepaw.org on 23 Jun 2010 at 3:41

GoogleCodeExporter commented 8 years ago
Actually, I may just be a moron: if I encode the textarea contents with 
htmlspecialchars first, then the contents are properly restored.  Otherwise, 
the browser unencodes the </> when displaying the textarea, and then jwysiwyg 
gets e.g. "<evil> and real" as the string for this.initialContent. There's 
probably no way to sort it out after it's been damaged like that.

Original comment by chad+goog@sapphirepaw.org on 23 Jun 2010 at 4:03