https://bugzilla.wikimedia.org/show_bug.cgi?id=26792
--- Comment #8 from MZMcBride <[email protected]> --- (In reply to comment #7) > Surely the person requesting this is the use case? Globals are annoying to maintain. My rough count in DefaultSettings.php at the time of this commit says there are about 730 global configuration variables. Before we add yet another, I'd like there to be a good reason. Database password, script path, etc. ... okay, that makes sense. But an option to disable an HTML comment from the parser output to a standard Web browser? Why? There's currently one comment from one user (comment 0) saying he or she wants to disable the HTML comment. We have a robust Web API that includes a flag specifically to disable this HTML comment in machine-readable HTML output. What more is needed here? If this still doesn't convince you, imagine you put every configuration variable next to a checkbox or drop-down menu in a graphical user interface. I doubt many people would think the additional user interface clutter is warranted here. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
