Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Content-Type: text/plain; charset="UTF-8"
Message-ID: <1957237.G35ZFXocOO@PointedEars.de>
From: Thomas 'PointedEars' Lahn <PointedEars@web.de>
Reply-To: Thomas 'PointedEars' Lahn <cljs@PointedEars.de>
Organization: PointedEars Software (PES)
Date: Sat, 22 Feb 2014 23:32:17 +0100
User-Agent: KNode/4.11.5
Content-Transfer-Encoding: 8Bit
X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&.<b';Md8`dH6iqhT)6C^.Px|[=M@7=Ik[_w<%n1Up"LPQNu2m8|L!/3iby{-]A+#YE}Kl{Cw$\U!kD%K}\2jz"QQP6Uqr],./"?;=4v
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXTxa4RFk5dUWANED8PFEfy7+MGBiW+n3ZNF/QuAAACaElEQVQ4jVXUwVOcMBQG8Dc7Rc4PUntdWV2uxjDpGaGeozOp1woar4jd5t/v9wLstMwsA/ntlxdCAgUc1hjTc9/JCZfGoo3wG3HdmdAWrIJRHe7GM/TmpY5VFefuVcAkkPbLIaN8rmPmjloyZxgyR3GuJ4K0AGtJ2htz8o7yqikm759fldQXaMpbDzjKAG+8v+AugVTOPO5DOjLvGtUYQwh0CPjnVMyGd+8/GfUB5nLKJDD2aLDh5HYyMDJGDwQIo2ZmZcKbowNmAdB/AzyFhrmF2MHRb0QJJfaAnwGB6orZhoykLzJtGwF/xpYxI1dswomiUj3gTuAIqCn/4C7cULwGNBtwMTk3Y4LfKB5YUaOKBKYtpplm7u0vip8tU1NWWyI/7XdcSuIDoMt6rVHMWT0DbjHPGqDqZVSa6zleLcUTcIKLoMv3ueJluALtAo9B302zPPlrtiVScRdCjXvVh3e3JpYa/jjkuC9N+LrBMlz/eAN4eQijX2EdLo6c5tGGHwLyHFtXk89dDGHwCVhG9T0S/j55AhRZgkMCmUQXJ49TnS1wnQDvw0eAh9ICeMmEFbCnPMFzjAvsWoEWEFdYEx+S0MoUZ1gT1wId8+AF3Bl2OoEu906AUHx5VLw/gXYg/x84loOah/2UYNrgiwSwGO7RfUzVBbx/kgpckumGOi6QirtD6gkLTitbnxNol47S2jVc2vsN5kPqaAHT8uUdAJM4v/DanjYOwmUjWznGfwB7sGtAtor5BgofDuzaRj4kSQAqDakTsKORa3Q3xKi3gE1fhl71KRMqrdZ2AWNNg/YOhQyrVBnb+i+nEg4bsDA+egAAAABJRU5ErkJggg==
Subject: Re: Get inner text of HMTL element
Newsgroups: comp.lang.javascript
References: <leambb$nfo$1@dont-email.me> <2186233.TZ7MnjCRox@PointedEars.de> <leb4g2$a1j$2@dont-email.me>
MIME-Version: 1.0
Lines: 79
NNTP-Posting-Date: 22 Feb 2014 23:32:19 CET
NNTP-Posting-Host: 3d83f28c.newsspool1.arcor-online.net
X-Trace: DXC=:f_bH<YS^LfEB;5>eE0T7mic==]BZ:afn4Fo<]lROoRankgeX?EC@@`\BGGOn[Md>hDZm8W4\YJNlYUVHKH;GI^g>8ZdD_1a;VhaU]>SjG;@Sh
X-Complaints-To: usenet-abuse@arcor.de
Xref: csiph.com comp.lang.javascript:23210

Cezary Tomczyk wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Cezary Tomczyk wrote:
>>> To get inner text of HTML element I've been using:
>>>
>>> function get_inner_text(node) {
>>>       if (node.nodeType === 3) {
>>>           return node.data;
>>>       }
>>>
>>>       var txt = '';
>>>
>>>       node = node.firstChild;
>>>       while (node) {
>>>           txt += get_inner_text(node);
>>>           node = node.nextSibling;
>>>       }
>>>       return txt.replace(/\s+/g, ' ');
>>                ^^^^^^^^^^^^^^^^^^^^^^^^
>> This is _not_ equivalent to node.textContent, see
>> <http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#Node3-textContent>.
> 
> I see. In documentation I've read that "No whitespace normalization is
> performed and the returned string does not contain the white spaces in
> element content[...]."
> 
> As for "whitespace normalization" I found that it's about "(spaces,
> tabs, and blank lines)" (http://www.w3.org/TR/REC-xml/#sec-white-space).
> However, "blank lines" means "new line" using \r\n or \r or \n, right?
> 
> Also, how "whitespace normalization" should work? E.g. replacing "   "
> to " "?

RTFSpec.  However, since it says there that “*no* whitespace normalization 
is performed” with “textContent”, you do not have to concern yourself with 
that in “textContent” emulation.

However, ISTM that at least Chromium “Version 32.0.1700.123 Debian 
jessie/sid (248368)” does not implement “textContent” as specified: “the 
returned string does not (read: MUST NOT) contain the white spaces in 
element content (read: “element content whitespace” as per XML), but it does 
there.  With

  var div = document.createElement("div");
  div.appendChild(document.createTextNode("  "));

  var span = document.createElement("span");
  span.appendChild(document.createTextNode("  "));

  div.appendChild(span);

“div.textContent” yields four spaces there, but IIUC should yield only two 
because the whitespace preceding the “span” element would be “element 
content whitespace” per XML.

<http://www.w3.org/TR/2004/REC-xml-infoset-20040204/#infoitem.character>

The reason for that may be that the first child object implements the Text 
interface of DOM Level 3 Core only incompletely: it implements the 
splitText() method introduced in Level 1 Core, and the “wholeText” attribute 
and replaceWholeText() method introduced in Level 3 Core; but it does not 
implement the “isElementContentWhitespace” attribute also introduced in the 
latter Specification.

<http://www.w3.org/TR/DOM-Level-1/level-one-core.html#ID-1312295772>
<http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-1312295772>

> Any suggestions?

Yes.

<http://www.catb.org/~esr/faqs/smart-questions.html>

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.