#1464: Unable to create <p> inside <div> (the return)
-----------------------------+----------------------------------------------
Reporter: designstack | Owner:
Type: Bug | Status: reopened
Priority: Normal | Milestone:
Component: UI : Enter Key | Version: FCKeditor 2.5 Beta
Resolution: | Keywords: Confirmed
-----------------------------+----------------------------------------------
Changes (by severy):
* status: closed => reopened
* resolution: fixed =>
Comment:
Replying to [comment:6 fredck]:
> Now, the only way to make users confused is by inputting code not
produced with FCKeditor. Alfonso exemplified it with templates. In this
case, the template itself is wrong. It must not contain an {{{<div>Type
here</div>}}} tag to indicate that you want a container there. It must
instead have {{{<div><p>Type here</p></div>}}}, so the template designer
intention is clear.
Frederico,
<sigh> I had fervently hoped that you would avoid falling into the trap
that every other WYSIWYG editor developer seems to fall into eventually,
by assuming that content is *only* created in your editor. While
FCKeditor is wonderful and all that, there is far more content out on the
net that is *not* created in FCKeditor. You can not ignore that reality
and basically say we only support content that was entirely created in
FCKeditor, which is basically what you are saying above. I'm sure I'm not
alone in using FCKeditor in a CMS that is designed to edit existing
content that was created long before the CMS was installed on the site.
It's not content that is created by templates in the editor, it's content
that was created by other editors or even Notepad.[[BR]]
[[BR]]
And most existing content on web sites is not created to follow the HTML5
standard, you're lucky if they even coded to the HTML4 standards. So
you're saying that FCKeditor will only support HTML5-coded web sites?
From my experience, most of the <div> tags on web sites on the Internet
*do* contain text or inline elements. And you're basically saying that
all of the web sites can not be edited in FCKeditor without the behavior
acting very strangely to the user, who doesn't know anything about HTML5
requirements or the arcane details of div rules, but simply expects the
Enter key to put in a <P> tag.[[BR]]
[[BR]]
So is it really that hard to add a configuration setting to allow this
behavior to work the way users would expect on a non-HTML5 web sites? If
a developer is using FCKeditor on a web site where all of the content is
created in the editor, leaving it as the current default may be fine. But
for the rest of the world, where we have to edit the content that already
exists, in whatever form it may be, we really, really need to be able to
configure FCKeditor to work the way the user would expect it to work.
Don't you agree?
--
Ticket URL: <http://dev.fckeditor.net/ticket/1464#comment:7>
FCKeditor <http://www.fckeditor.net/>
The text editor for Internet
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
FCKeditor-Trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac
