Change Details

During parsing and running various transformations, Parsoid has sufficient information about buggy wikitext usage that can be passed back to editors for fixing up (Ex: fostering of content out of tr-rows because of missing td-wikitext tags, or missing newlines, etc). This can also be a good way to slowly deprecate reliance on edge case behavior by editors (Ex: multi-comment whitespace lines are treated different from single-comment whitespace lines -- this is just a side effect of PHP parser code and should be made consistent in the parser after deprecating its usage). This is more a longer-term goal and can be a good self-contained project for someone. -------------------------- **Version**: unspecified **Severity**: normal **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=50547 https://bugzilla.wikimedia.org/show_bug.cgi?id=62323 https://bugzilla.wikimedia.org/show_bug.cgi?id=66413

During parsing and running various transformations, Parsoid has sufficient information about buggy wikitext usage that can be passed back to editors for fixing up (Ex: fostering of content out of tr-rows because of missing td-wikitext tags, or missing newlines, etc). This can also be a good way to slowly deprecate reliance on edge case behavior by editors (Ex: multi-comment whitespace lines are treated different from single-comment whitespace lines -- this is just a side effect of PHP parser code and should be made consistent in the parser after deprecating its usage). This is more a longer-term goal and can be a good self-contained project for someone. ---- See also: * {T52547} * {T64323} * {T68413}

During parsing and running various transformations, Parsoid has sufficient information about buggy wikitext usage that can be passed back to editors for fixing up (Ex: fostering of content out of tr-rows because of missing td-wikitext tags, or missing newlines, etc). This can also be a good way to slowly deprecate reliance on edge case behavior by editors (Ex: multi-comment whitespace lines are treated different from single-comment whitespace lines -- this is just a side effect of PHP parser code and should be made consistent in the parser after deprecating its usage). This is more a longer-term goal and can be a good self-contained project for someone. -------------------------- **Version**: unspecified **Severity**: normal **See Also**: See also: https://bugzilla.wikimedia.org/show_bug.cgi?id=50547* {T52547} https://bugzilla.wikimedia.org/show_bug.cgi?id=62323* {T64323} https://bugzilla.wikimedia.org/show_bug.cgi?id=66413* {T68413}