Krinkle wrote:
On Oct 18, 2012, at 5:04 AM, Daniel Kinzler daniel@brightbyte.de wrote:
When designing the ContentHandler, I asked around about whether JS and CSS pages should be parsed as wikitext, so categories etc would work. The gist of the responses I got was "naw, lets get rid of that". So I did (though PST is still applied - Tim asked for that at the Berlin Hackathon).
Sure enough, people are complaining now, see https://bugzilla.wikimedia.org/show_bug.cgi?id=41155. Also note that an older request for disablingt parsing of script pages was closed as WONTFIX: https://bugzilla.wikimedia.org/show_bug.cgi?id=32858.
I'm inclined to (at least optionally) enable the parsing of script pages, but I'd like to get some feedback first.
Yeah, as more elaborately put on the bug[1], it was disabled in ContentHandler without dedicated discussion because it was thought of as a minor oddity that should be removed as a bug.
We know now that (though it might have been a bug originally) it is a major feature that unless replaced, must not be removed.
Well, the current approach is hackish. The links are kind of stored, but not rendered, so you still end up with dead-end pages and a completely surprising result to most users.
I think the last thing we need is yet another parser. There is already distinct parsing for weird parts of the MediaWiki UI (such as edit summaries and log comments). I think any further specialized parsers should be shot on-sight.
More thoughts here: https://bugzilla.wikimedia.org/39609 ("Limit scope of title-based syntax highlighting").
MZMcBride