Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Arno Welzel Newsgroups: comp.lang.javascript Subject: Re: innerHTML Date: Wed, 04 Jan 2012 08:54:29 +0100 Organization: A noiseless patient Spider Lines: 30 Message-ID: <4F0405B5.1010706@arnowelzel.de> References: <36r7f719terpj6d2guc8v2hicvnmsgilvc@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Injection-Info: mx04.eternal-september.org; posting-host="Psb2+p0U7wkhKleuxO8/EQ"; logging-data="22280"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/dHVveiPET7U8GQ1OwG4LCxO4GG5tnjJU=" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 In-Reply-To: <36r7f719terpj6d2guc8v2hicvnmsgilvc@4ax.com> Cancel-Lock: sha1:kKR6mluh4OudVea5f046BkbJZA4= Xref: x330-a1.tempe.blueboxinc.net comp.lang.javascript:9906 Gene Wirchenko, 2011-12-23 03:55: > Dear JavaScripters: > > The FAQ states: > 9.4 How do I modify the content of the current page? > Using the non-standard but widely implemented innerHTML property... > > Is it still the case that it is non-standard? Is there an > alternative that is standard? With HTML5 innerHTML will become a standard. See also: Anyway - the problem remains, that you may end up with an invalid document when you insert invalid markup using innerHTML and the browser has to parse the given markup with every change of the innerHTML property. For more complex stuff you should use the DOM methods. This will be faster and you can not create invalid documents accidentally. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de