#1464: Unable to create <p> inside <div> (the return)
-----------------------------+----------------------------------------------
Reporter: designstack | Owner:
Type: Bug | Status: closed
Priority: Normal | Milestone:
Component: UI : Enter Key | Version: FCKeditor 2.5 Beta
Resolution: fixed | Keywords: Confirmed
-----------------------------+----------------------------------------------
Changes (by fredck):
* status: reopened => closed
* resolution: => fixed
Comment:
Before continuing, let me highlight that I'm not here to push my personal
point of view. I prefer taking decisions over tangible arguments, not only
based on personal assumptions.
Replying to [comment:7 severy]:
> 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. (...) 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.
Please don't put words in my mouth. I've only explained how things are
done in the editor and the reasons for it. I've also explained the way we
handle content not produced with the editor, also explaining the reasons
for it.
> So you're saying that FCKeditor will only support HTML5-coded web sites?
Again, I've never told that. I've pointed to HTML5 because that standard
gives us some better understanding of <div>, while HTML4 is limited to its
syntax only. The HTML4 standards is quite limited in the semantics point
of view.
> most of the <div> tags on web sites on the Internet *do* contain text or
inline elements
Ok, and most of them are not there to hold block elements, but text and
inline elements. There is no magic here... there must be some rules to
understand which div is for inline content, and which one is for blocks.
> 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.
> we really, really need to be able to configure FCKeditor to work the way
the user would expect
Again, more words put on my mouth...
Well... here, you are really reading users' minds. You can't just say what
users want it in this way. Because this is not always true. And the same
user who says that s/he needs it, will later say that it should be other
way "also".
Here again. Put yourself in the editor shoes... is the following div
intended to hold inline stuff or blocks: {{{<div>by Bruce Lee</div>}}}.
What should we have on enter at the end of it?
{{{
<div>by Bruce Lee</div>
<p></p>
}}}
... or:
{{{
<div>
<p>by Bruce Lee</p>
<p></p>
</div>
}}}
... or even:
{{{
<div>by Bruce Lee</div>
<div></div>
}}}
There is no way to know what the user expects here. There is nothing there
saying that it should hold blocks. As it has text only, all we can do is
assume it has to be inline.
Then, at the same time, we can have mixed situations, like the following:
{{{
<div class="title">About Bruce Lee</div>
<div class="body">Bruce Lee was an American-born martial artist...</div>
}}}
Here, users (the rest of the world) will tell you that they want the
editor to magically understand that the first div is not supposed to
contain blocks, while the second should have them. What to do in this
case? Start crying? No! We must instead explain things well, making it
clear that they will be facing such issues because of technical problems
introduced with content produced previously. Then, explain them how to fix
it. As things get fixed, they will just have a better editing experience,
making their content better at the same time.
> Since you mentioned a misunderstanding about your reference to HTML5,
I've been doing some research on this area to learn more about it.
It was not intended to say that you have limited HTML5 knowledge. I was
saying that you have misunderstood the way I've referenced to it in my
comment, as I'm not saying that our content is targeted to HTML5. Sorry
for another misunderstanding.
----
Now two notes.
One thing that can be definitely considered instead is a way to make sure
that <p> will be produced when pressing ENTER and EnterMode="p". Ticket
#2403 should address this issue.
Please do not reopen this ticket just to add further comments. It has been
closed because there is currently a way to create <p> inside <div>. Other
things should be discussed in the proper place, as explained in my
previous comment.
--
Ticket URL: <http://dev.fckeditor.net/ticket/1464#comment:9>
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
