Support was added to master in I9ee852e33412826608b6039fa01a2b0027b35e7b, should also be supported in 2.0. We don't need the legacy hook, because Gadgets 2.0 stops supporting legacy gadgets.
Description
Description
Details
Details
- Reference
- bz69681
Related Objects
Related Objects
- Mentioned Here
- T127268: Dismantle ResourceLoader's "targets" system
Event Timeline
Comment Actions
Removing the Gadgets 2.0 relationship from this bug. Adding such property to the gadget definition is trivial to do in both v1 and v2.
However I'm blocking this on consensus and discussion with someone from Mobile Web. I'm not sure they are ready to support gadgets being loaded on mobile pages (and loaded by default). Currently Common.js and most other site customisations are still disabled.
We need better insight into what the community needs and should collaborate and educate there before opening this up.
Comment Actions
targets support already exists in v1, this bug is about not causing a regression in v2.
Comment Actions
I'd love to see mobile support for Gadgets. In commons we have a bunch of user interface enhancements that would translate to the mobile version (like the "Good Pictures" button: https://commons.wikimedia.org/wiki/Help:FastCCI).
Comment Actions
To clarify, Gadgets can already run in mobile mode by adding targets=mobile|desktop to their definition. This bug is about adding that functionality to the 2.0 codebase so we don't regress..