From https://www.mediawiki.org/wiki/ResourceLoader/V2_Task_management:
(RK) Figure out how gadget ID naming collisions should be handled, define this somewhere, and enforce it
I think local gadgets should take precedence, and then give precedence to whatever shared repo is first in $wgGadgetRepositories.
Version: unspecified
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T34169 Action to join scripts and styles in one file | |||
| Open | None | T110014 Make gadgets easily customizable (merge Gadgets' branch "gadgetprefs" from GSoC 2011) | |||
| Open | None | T31272 Implement Gadgets 2.0 | |||
| Declined | Legoktm | T72824 2.0 Figure out how gadget naming collisions should work, and document it |
Hmm, something else I thought of. Right now if a user enables a gadget "foo", and a repo higher up in the precedence chain creates a gadget named "foo" as well, the user will now get the JS/CSS from the new repo instead of what they actually enabled. If we make the local repo highest priority, a local gadget-manager could override popular global gadgets in this form to hypothetically compromise accounts. Or something not so good.
Possible solution: Embed the repo name in the preference key, so that if the source of a gadget changes, the user won't keep the same preference value. Might be a bit confusing from a UX perspective.