Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.javascript Subject: Re: InnerHTML quirks Date: Thu, 27 Jun 2019 11:01:35 +0200 Lines: 10 Message-ID: References: <6dcae054-0a58-4000-9bb0-0be37a937500@googlegroups.com> <8b7e4e9a-6254-44c6-b06e-fdbec9930b32@googlegroups.com> <9edf6537-5c4a-4259-8f47-1d6c2caad683@googlegroups.com> <0fad35b3-a158-47f3-82d8-00e86849ac8b@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net yCx27QD9Ku40wsCITCIwAQrQH3d+rz9Aoth6vobCtaivCuLkiO Cancel-Lock: sha1:g1PUD1WMz1w7qqPLpCwLBqYmlCs= In-Reply-To: <0fad35b3-a158-47f3-82d8-00e86849ac8b@googlegroups.com> Content-Language: en-US Xref: csiph.com comp.lang.javascript:36944 On 27.06.19 10:59, Jonas Thörnvall wrote: > This is just one of a million negative effects of the parent->child methodology used for dynamically generate "HTML text"; Then use the DOM to create elements! You don't have to use innerHTML at all. -- Arno Welzel https://arnowelzel.de