Am 16.02.2014 10:32, schrieb David Gerard: > There are extensions that allow raw HTML widgets, just putting them > through unchecked.
I know, I wrote one :) But that's not the point. The point is maintaining editable content as HTML instead of Wikitext. > The hard part will be checking. Wikitext already allows a wide range of HTML tags, and we have a pretty good sanitizer for that. Adding support for a few additional structures (like links and images) and the extra data embedded by/for parsoid should not be a lot of work. > Note that the > rawness of the somewhat-filtered HTML is a part of WordPress's not so > great security story (though they've had a lot less "update now!" in > the past year). So, may not involve much less parsing. I think it would, since it doesn't add much to the sanitizer we use now, but reducing the amount of parsing wasn't the point. The point was avoiding conversion, which is potentially lossy and confusing, and essentially pointless. If we edit using an HTML ewditor, why not store HTML, make (structural) HTML diffs, etc? It just seems a lot more streight forward. -- daniel _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
