> > As I understand, the 'targets' system was put in place to prevent > mobile-inappropriate modules from being loaded by default. But this is not > loaded by default; as you point out, there's an explicit mw.loader.using() > call that specifies the module by name and causes to be retrieved on > demand. For MobileFrontend to pretend that the module doesn't exist at that > point seems like a design flaw of the targets system. I'm happy to specify > mobile as a target for this module, but I think this is a point of friction > between ResourceLoader and MFE that will continue to be a source of > problems until it is resolved. >
Agreed on all points. Unfortunately it was the only real option at the time to ensure incompatible JavaScript/css wasn't added from other extensions / existing code / gadgets. The plan is for it to eventually die but inspect helps exactly with achieving that by highlighting what is loaded by default and weeding out what is suitable for mobile and what is not. I do wonder if there is a way for targets to only apply to initially loaded modules and whether this is a good idea knowing some modules will be broken in this view. _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
