So we're building error reporting into HTML Purifier, and the current setup is simply to tell the user any changes that HTML Purifier made to the HTML in order to make it standards compliant.
While hacking on it, I realized that there was another mode of operation, the "standards-checker" type, where we point out errors to users and suggest changes. Right now, we have almost entirely suggestions (i.e. what HTML Purifier did), and no proper "error" reporting.
What would you all say is the most user friendly approach?
User friendly HTML input
Moderator: General Moderators
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US