Path: csiph.com!aioe.org!news.mb-net.net!open-news-network.org!.POSTED.100.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: Re: Inserting a DIV inside another DIV Supersedes: <10929581.O9o76ZdvQC@PointedEars.de> Date: Sun, 27 Aug 2017 03:16:57 +0200 Organization: PointedEars Software (PES) Lines: 57 Message-ID: <5095798.DvuYhMxLoT@PointedEars.de> References: <6711ac96-c627-4e0c-b267-6a7602e0cdc5@googlegroups.com> Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit Injection-Info: gwaiyur.mb-net.net; posting-host="100.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch:178.197.225.100"; logging-data="6929"; mail-complaints-to="abuse@open-news-network.org" User-Agent: KNode/4.14.2 X-User-ID: U2FsdGVkX1/p4O1VPBdZKffV64QTMnPV9P5uvpaBxRGyUSHna7Hcuw== Cancel-Lock: sha1:85nz87JLJxQDWdfyrxS+whjXG6g= X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. On 25/08/17 07:16, bit-naughty@hotmail.com wrote: > [snip] >> Umm *bro*, if one should call you that, it's the "appending it INSIDE" >> part that confuzzles me: > > Yes, it's confusing if you don't understand this kind of markup. > Doubly confusing because the designer who chose that phrase also didn't > understand this kind of markup — you are correct, one does not "append" > inside an element, one "inserts". One "appends" to a list; if there is > nothing to append to, it makes no sense touse the word "append". > > But we're stuck with it, I'm afraid. > > Moral of the story if that designers of languages need to read the spec > and understand the structure and syntax of the data they are planning to > deal with. Utter nonsense. By calling the appendChild() method of an element object, one appends a child node to the list of child nodes of an element node, accessible with the “childNodes” property of that object, which in turn refers to an object that ought to implement (at least) the NodeList interface. p. > [snip] >> I find that very confusing - you're calling something INSIDE div2 , >> instead of div2 being an *argument*!! I would have thought that if >> you want something inside "div", you tell it 1) what you want, and 2) >> inside what, i.e. BOTH of them would be arguments. ...Me not the OOP >> fanatic, remember....? THAT's the main reason for all the >> questions..... > > That's part of the flawed syntax of Javascript, unfortunately. Sadly, you have not the slightest clue what you are talking about. I strongly suggest you be silent until this has changed, in order not to confuse people, especially those who are very confused already. To begin with, there is no “Javascript” (see sig). The interfaces we are discussing in this thread, and their implementations, are not even part of any ECMAScript implementation such as the language*s* that have “JavaScript” in their name. The DOM is a *language-neutral* API; one can merely *access* its *implementations* by using an ECMAScript implementation, *among other programming languages*. > [further misconceptions of a wannabe] -- PointedEars FAQ: | | Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.