Page MenuHomePhabricator

Display Categories on top of pages (but below images) at Commons
Open, LowestPublic

Description

See proposal at Commons: Categories have evolved to be the main tool for organizing content at Commons. However, they are by default placed at the very bottom of the file description page, where hardly anyone who's not looking for them will ever find them. There already is a gadget called Place categories above content, but below image on file description pages and consensus to enable it seems pretty clear to me. Could possibly resticted to content namespaces (files, categories, galleries; possibly graphs in the future)

It was pointed out that just enabling the js gadget per default would be a bad idea for technical (?) reasons: "This needs a integration in MediaWiki to avoid Jumping Content."

Event Timeline

El_Grafo raised the priority of this task from to Needs Triage.
El_Grafo updated the task description. (Show Details)
El_Grafo added projects: Commons, Gadgets.
El_Grafo added subscribers: El_Grafo, Steinsplitter, Rillke.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 17 2015, 11:44 AM
Steinsplitter moved this task from Incoming to Backlog on the Commons board.Jun 17 2015, 11:46 AM
Aklapper set Security to None.

Removed Gadgets from this task as this is unrelated to the code of the MW extension called "Gadgets".

Not sure how this request could/should be implemented though. :(

zhuyifei1999 added a comment.EditedJun 17 2015, 12:47 PM

Implement via MediaWiki core (or skin) and add a new configuration variable?

Revent added a subscriber: Revent.Jun 19 2015, 10:15 PM

Could someone maybe explain how bad enabling the JS gadget by default would really be? I've been using it for years and it works flawlessly. Are there any real disadvantages or is it just a matter of bad style? Is it really worth waiting (possibly years) for this to be implemented in MediaWiki, when the problem could be solved by simply flicking a switch?

Steinsplitter added a comment.EditedJun 23 2015, 3:59 PM

Could someone maybe explain how bad enabling the JS gadget by default would really be? I've been using it for years and it works flawlessly. Are there any real disadvantages or is it just a matter of bad style? Is it really worth waiting (possibly years) for this to be implemented in MediaWiki, when the problem could be solved by simply flicking a switch?

Jumping content, especially if your browser isn't fast. If you have disabled JS, then it does not work. It also means moor load on resource loader. And it is a ugly hack, locks very unprofessional.

If you like to have this fixed soon you should probably find a volunteer which can provide the code.

Aklapper triaged this task as Lowest priority.Jun 29 2015, 11:00 AM
Aklapper removed a project: patch-welcome.
Perhelion added a subscriber: Perhelion.