https://bugzilla.wikimedia.org/show_bug.cgi?id=31958
--- Comment #2 from Gregor Hagedorn <[email protected]> 2011-10-26 20:15:57 UTC --- > Why would you want per-page JS? What kind of use case does this address that > Gadgets doesn't already address? It would allow specific functionality needed only on certain pages to be tested and deployed only on these pages (and tested on yet a subset of those). This would allow specific code (interactive timeline, decision trees (click on http://species-id.net/wiki/Philaccolilus#Key on "Step-by-step identification" - the Javascript is needed only page having such a decision tree, but must be globally deployed), special galleries, etc. The enable the community to develop functionality needed by the community that is either not foreseen by developers, or not implemented due to resource constraints. Mediawiki is a publishing platform, but gadgets provide only authoring tools. Even there they are used only by a tiny fraction of editors. They are important and provide an agile development path for code later to be widely deployed. But I believe they don't cover any reader experience. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- 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
