Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:32971 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5674 invoked by uid 1010); 24 Oct 2007 19:33:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 5659 invoked from network); 24 Oct 2007 19:33:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2007 19:33:09 -0000 Authentication-Results: pb1.pair.com header.from=gunther@keryx.se; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=gunther@keryx.se; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain keryx.se designates 208.69.121.33 as permitted sender) X-PHP-List-Original-Sender: gunther@keryx.se X-Host-Fingerprint: 208.69.121.33 supavet.nexcess.net Received: from [208.69.121.33] ([208.69.121.33:41316] helo=supavet.nexcess.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/B7-47805-2FD9F174 for ; Wed, 24 Oct 2007 15:33:08 -0400 Received: (qmail 30749 invoked by uid 108); 24 Oct 2007 19:33:03 -0000 Received: from unknown (HELO ?127.0.0.1?) (gunther@keryx.se@87.227.57.139) by supavet.nexcess.net with ESMTPA; 24 Oct 2007 19:33:03 -0000 Message-ID: <471F9DED.9050008@keryx.se> Date: Wed, 24 Oct 2007 21:33:01 +0200 User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: PHP Developers Mailing List References: <471F08B4.6080400@keryx.se> <471F18E0.6080602@ctindustries.net> In-Reply-To: <471F18E0.6080602@ctindustries.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000783-1, 2007-10-22), Outbound message X-Antivirus-Status: Clean Subject: Re: [PHP-DEV] DOM shortcuts From: gunther@keryx.se (Lars Gunther) Rob Richards skrev: > These would most certainly not make the standard. The first already > exists in the form of textContent in Level 3 specs. The first one was not on my agenda. Sorry for my lack of clarity. > The second is a > limited piece of functionality for creating content within an element. > Although this is the type of document the majority of PHP developers are > using (only basing this on experience and feedback from people), content > is sometimes much more complex than this, so I doubt a parameter > limiting functionality this much would be added. > I do think JavaScripters (et al) will enjoy the same convenience! Many PHP-developers write JavaScript, too. In what way will the second parameter *limit* functionality, if it's optional? Going off topic: If anyone is interested, here is the link to the discussion I started on the WHAT-WG mailing list: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-October/012841.html As an example of why I think WHAT-WG is an appropriate place to suggest this feature is the new method getElementsByClassName. Firefox 3.0 will the first browser to support the this addition to the W3C-DOM spec. Opera and Safari will soon follow as there are great speed improvements to be won having it natively: http://ejohn.org/blog/getelementsbyclassname-speed-comparison/ Lars Gunther BTW, Rob, I've read your book. Great stuff!