Thread:Fandyllic/@comment-27075564-20170724155029/@comment-1077307-20180123195623

I think I failed to understand the depths of the mobile theme lockdown. I see a possible path for workaround, but even if it works its clear the wikia intent is to close those kinds of loopholes.

So the only real and compliant fix would be to generate a static composite image for mobile when the template runs and would only be useful for the embedded map. Since the template and other server side code it still allowed to run, and since the templates as written are cacheable, Lua would be fast enough and capable of submitting a new image or replacing an old one. The downside is that each time someone changed the map a new image revision would get generated and although it would probably be rather rare, I hesitate to add something that if the code was changed and someone didn't understand the way the cache was being tracked that it would litter the server with countless revisions. This assumes there is no way to tell wikia to not keep revisions of an image or to truly delete an image.

So I'll fish around and consider maybe some other ideas. But the fundamental issue is anything delivered by wikia image cache servers needs to go though the change history. Anything that is wiki specific css or js is intended to not exist on mobile.