https://bugzilla.wikimedia.org/show_bug.cgi?id=40033
--- Comment #2 from Jon <[email protected]> 2012-09-06 17:25:17 UTC --- I agree that "it is perfectly possible for code to work fine in both mobile and desktop" however the thing I'm trying to protect against is the situation where we enable resource loader and then have to spend time vigorously testing code on the mobile site. There is also a danger that some code will just not be useful on mobile. * For instance on the desktop when hovering over a reference a popup shows - hover effects will not work on mobile therefore this code is adding bloat. * Personally I think mobile feedback in it's current form is not suitable for mobile - it needs to be presented in a different way as on a mobile device in its current form it takes up a lot of real estate. This in itself is a huge task on the article feedback extension and would delay resource loader migration. Trying to QA and improve all existing extensions would be a mammoth task and the migration would never be done as we would be forever blocked by issues in javascript modules which break or do not work on obscure mobile devices. We can do this but __this is not an agile way of doing things__. In the interest of moving forward quickly I therefore believe it is __vital__ that we have some mechanism to whitelist/blacklist modules. I had suggested extensions registering themselves as mobile suitable but a whitelist/blacklist in a config file would also do. I see things working like this: 1) Migrate to full blown resource loader with all javascript modules disabled. 2) Review modules and vigourously test them one mondule at a time raising and fixing blocking bugs 3) Enable modules when confident they work across mobile devices AND make sense on a mobile device. Not doing this would be a recipe for disaster and from experience will take much longer than it needs to. -- 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
