https://bugzilla.wikimedia.org/show_bug.cgi?id=58478
--- Comment #1 from Brion Vibber <[email protected]> --- A couple possible scenarios: 1) Always load just enough code to check for if you need to do runtime JS transformations In this scenario, every page that can show wikitext should have at least a tiny JS module loaded that hooks into an event that is called on load and again every time new parsed wikitext output is added to a page (such as by a preview, or a dialog box, or whatever). This might be a very tiny piece of code that just asynchronously fires off a load of a fuller module, such as something that adds player controls to a video or sets up interactive rendering of a molecule on a canvas, or whatever, when it encounters its targets (and otherwise does nothing). Advantages: * can use same code & event for initial load and new loads? * defers extra media modules until use * doesn't require recording modules used per page 2) Implement any media viewers more complicated than a simple element without scripting via an <iframe> Advantages: * the iframe content rendering worries about module loading, the parent page can ignore it totally * makes exposing those media for external embedding trivial, as we'd be doing the exact same thing we do in our content context -- 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
