Recently CSS & JS pages have been blocked from custom rendering and are rendered in monospace font with syntax hiliting. Although syntax hiliting is nice, this hardcoded behavior is not user friendly (besides it can be solved by wrapping the entire page in <pre> or <source>). Bug 10410 and bug 10422 show I'm true.
So I propose different approach to these pages which brings much better user friendliness:
Either
- add switch view pulldown to the header of CSS/JS pages to select regular wiki / pre / syntax hilite style of rendering - a bit similar to Special:Allmessages where you can choose either table or PHP view
Or
- add new preference called "Render CSS/JS pages as:" and the pulldown described above.
Let the user decide which style he likes.
(choose the way which is simplier to implement or suggest other with similat principle - user's ability to choose, I'd prefer user preferences because it will be global behavior setting, or both so user can override global behavior on such page temporarily)
PS: Why wikitext, pre and syntax hilight and not only wikitext and syntax hilight? Because syntax hilight produces hell-a-long pages while pre style with same view (monospace font) is much much shorter.
Version: 1.21.x
Severity: enhancement
URL: https://en.wiktionary.org/wiki/Module:languages