Todo List
HTMLPurifier
- Make it private, fix usage in HTMLPurifier_LanguageTest
- This really ought to be protected, but until we have a facility for properly generating HTML here w/o using tokens, it stays public.
- Consider making protected
- Implement conditionals? Right now, some messages make reference to line numbers, but those aren't always available
- Throw an exception if file doesn't exist
- We need an easier way to inject strategies using the configuration object.
- whitelisting allowed fonts would be nice
- Create a separate maintenance file advanced users can use to cache their custom HTMLDefinition, which can be loaded via a configuration directive
- Implement memcached
- Make some of the more internal functions protected, and have unit tests work around that
- Refactor interface so that configuration/context is determined upon instantiation, no need for messy generateFromTokens() calls
- Consider making some member functions protected
- Figure out how to protect some of these methods/properties
- Allow injectors to request a re-run on their output. This would help if an operation is recursive.
- Serialized cache for languages
- Reread XML spec and document differences.
- Generalize so that XML_HTMLSax is also supported.
- Enable nodes to be bubbled out of the structure.
- Port DirectLex to use this
- Filter allowed query parameters
- Validate the email address
- Also add information about internal state
- Consider making protected
- Give this its own class, probably static interface
- Extend to indicate non-text/css style blocks
- Wildcard matching and error reporting when an added or subtracted fix has no effect.
- Refactor duplicate elements into common class (probably using composition, not inheritance).
Documentation generated on Thu, 19 Jun 2008 18:50:33 -0400 by phpDocumentor 1.4.2