contentEditable字段，用于在数据库输入时维护换行符-contentEditablefieldtomaintainnewlinesupondatabaseentry

23  

jQuery uses textContent on a Node to return the text value of an element, which will compress white space. If you want the line breaks to be maintained, you need to use innerText which means accessing the element directly rather than through jQuery.

jQuery使用Node上的textContent来返回元素的文本值,这将压缩空白区域。如果你想要维护换行符,你需要使用innerText,这意味着直接访问元素而不是通过jQuery。

From your jsfiddle:

从你的jsfiddle:

console.log($(Comments)[0].innerText);

http://jsfiddle.net/M8wx9/10/

==== update:
As a caveat to this (as Tim Down has pointed out), using innerText will only work in webkit and microsoft browsers. If your application also supports Firefox, you will need to use regular expressions on the innerHTML in order to maintain line breaks. As an example:

====更新:作为对此的一个警告(正如Tim Down指出的那样),使用innerText只能在webkit和microsoft浏览器中使用。如果您的应用程序也支持Firefox,则需要在innerHTML上使用正则表达式以保持换行符。举个例子:

$(Comments).html().trim()
   .replace(//ig, '\n') // replace single line-breaks
   .replace(/<[p|div]\s/ig, '\n$0') // add a line break before all div and p tags
   .replace(/(<([^>]+)>)/ig, "");   // remove any remaining tags

http://jsfiddle.net/M8wx9/12/

1  

function readContentWithBreaks(elem){
  if(elem[0].innerText){
    return elem[0].innerText.replace(/\n/ig,"
");
  }else{
    return elem.html();
  }
}

Since webkit browsers support innerText I decided to detect for that swap the /n they add. For Firefox it already gives the content with
so we can just take it as-is.

由于webkit浏览器支持innerText,我决定检测它们添加的/ n。对于Firefox,它已经为内容提供了
所以我们可以按原样使用它。

-1  

This sounds too simple, so I am hesitant in giving this answer, but from a quick test I ran, the following should work perfectly all right (in chrome at least):

这听起来太简单了,所以我对这个答案犹豫不决,但是从我跑的快速测试来看,以下应该可以完美地工作(至少在chrome中):

$(".post-text").text().replace(/\n/g,"
")

You do have to start with a separate p or div tag though, so a text node followed by a paragraph element will not generate a line feed character.

您必须从单独的p或div标记开始,因此文本节点后跟段落元素将不会生成换行符。

And a jsfiddle shoing this. Still, as you already mention contentEditable isn't extremely cross browser consistent... so it might be a good idea to use an existing editor really.

并且有一个jsfiddle嘲笑这个。尽管如此,正如您已经提到的,contentEditable并不是非常跨浏览器的一致性......因此,真正使用现有编辑器可能是个好主意。