Difference between revisions of "Topsoil HTML Filter"
Brandon Bot (talk | contribs) (Refactored to use standard open task categories Category:OpenTask, Category:DevelopmentTeam) |
|||
|
(8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude><big>[[ | + | <noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''5''') [[Topsoil HTML Filter]] ('''[[Who?|?]]''') {{JustTinyEditIcon|Topsoil HTML Filter}}<noinclude></big> |
| − | </noinclude>[[Topsoil HTML Filter]] (''' | ||
__NOTOC__ | __NOTOC__ | ||
== What (summary) == | == What (summary) == | ||
| Line 18: | Line 17: | ||
* lib_filter.php | * lib_filter.php | ||
| − | [[ | + | == Discussion == |
| − | [[Category: | + | * How does this fit in with our desire to allow users to completely customize the entire skin? [[User:Jason Parmer|Jason Parmer]] 16:39, 30 August 2007 (PDT) |
| − | [[Category: | + | ** This will apply to the content that lives in the commons (e.g., anything under http://www.aboutus.org/). It needs to all have a consistent, highly skinnable structure so that trees (sites that mount the commons under their own url) can easily customize the presentation. |
| + | |||
| + | [[Category:OpenTask]] | ||
| + | [[Category:DevelopmentTeam]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 21:02, 7 February 2008
What (summary)
A Ruby implementation of a filter that passes a well-known set of tests that prevent users from altering the styles and scripts that control how content looks on our site.
This is a server side tool that allows users to submit rich content (e.g., html) without introducing security risks to the system or other users.
Why this is important
It's enabling server side technology for an HTML representation of wiki content. The problem it solves is preventing security abuses and restricting HTML usage to forms that we can understand. Flickr uses a php implementation that passes all of the same tests as the python HTML Filter. Our Ruby version will also pass these same tests.
DoneDone
- All python or php tests are converted to Ruby
- Ruby implementation passes all of the converted tests
Notes
- http://amisphere.com/contrib/python-html-filter/
- lib_filter.php
Discussion
- How does this fit in with our desire to allow users to completely customize the entire skin? Jason Parmer 16:39, 30 August 2007 (PDT)
- This will apply to the content that lives in the commons (e.g., anything under http://www.aboutus.org/). It needs to all have a consistent, highly skinnable structure so that trees (sites that mount the commons under their own url) can easily customize the presentation.