#1905: POSTed data sometimes HTML encoded sometimes not
---------------------------------+------------------------------------------
Reporter: Kyle | Owner:
Type: Bug | Status: reopened
Priority: Normal | Milestone:
Component: Core : Output Data | Version: SVN
Resolution: | Keywords: Confirmed
---------------------------------+------------------------------------------
Comment (by Kyle):
Replying to [comment:2 fredck]:
> Replying to [ticket:1905 Kyle]:
> > 'This is < & > " some..." which is what it should always be.
>
> This assumption on totally wrong. It is definitely correct to encode
those chars.
It is NOT at all correct to encode those characters. Here's a different
take on it if you don't buy the Source vs WYSIWIG argument.
1. Use a standard <textarea> in a form. If you type in 'This < & > "
some...' in the textarea and submit the form, then the POSTed data will be
'This < & > " some...' No surprises. It's exactly what the user typed.
2. Use a standard FCKeditor in a form. Leave it in WYSIWIG mode. If you
type in 'This < & > " some...' in the FCKeditor and submit the form, the
POSTed data will be 'This < & > " some...' This is a huge
surprise and is NOT what you typed in.
If FCKeditor is supposed to be a drop-in replacement for <textarea>
elements, then it should not encode characters as HTML entities that the
user types in.
--
Ticket URL: <http://dev.fckeditor.net/ticket/1905#comment:4>
FCKeditor <http://www.fckeditor.net>
The text editor for Internet
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
FCKeditor-Trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac
