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!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
