The exception in the console halts the render, so nothing shows up at all on the page.

This only works in the mobile interface, so ensure you are using the mobile skin (?useskin=fandommobile)

https://dev.fandom.com/wiki/User:MrAwesome8/PortableInfobox

The first one should appear and the second one should not. The second one is what throws an exception when the skin is fandommobile.

Thanks for the example. I now understand that you're talking specifically about portable infoboxes created by Lua - it wasn't clear from your original post.

Bottom line, you've indeed spotted a problem - portable infoboxes generated by Lua aren't rendered on the mobile skin (see some more technical details below).

I would say it's not very surprising. There are three different extensions involved: PortableInfobox, Scribunto and MobileFrontend - all three do complex parsing of content. Probably best you can do is file a report to Fandom, but I doubt they'll prioritize it.

Now a few technical details for anyone interested:

I've copied your example code to Dev_Wiki:Sandbox because there's no way to view user pages in the mobile skin.

I've tested two versions of it:

https://dev.fandom.com/wiki/Dev_Wiki:Sandbox?oldid=207658&useskin=fandommobile - an exact copy of your code example.

https://dev.fandom.com/wiki/Dev_Wiki:Sandbox?oldid=207659&useskin=fandommobile - to make sure that the issue isn't about which infobox comes first or the number of infoboxes (generally, the FandomMobile skin does treat the first infobox in a page differently than the others).

Another point to note is that the issue isn't with the JavaScript but with the original HTML generated on the server. Infoboxes don't need JS to be displayed, the JS just does some extra refinements. The error you're seeing is the JS trying to access the non-existing infobox, but no change in the JS can solve the issue.

Thanks for looking into it and verifying the behavior. I suppose I'll roll my own custom mobile infobox then. Thanks.

One more thing to try, if the main thing you need is dynamically generate the infobox with Lua, is to only generate the inner part, like this:

{{#tag:infobox| {{#invoke:MODULE | FUNCTION }} }}

Were you able to get this to work? I tried playing around with it and numerous variations but without success.

Okay scratch that... the issue does not exist in the first place. Infoboxes generated by Lua are displayed perfectly fine on mobile, as can be seen here: https://dev.fandom.com/wiki/Dev_Wiki:Sandbox?oldid=207688&useskin=fandommobile

The issue with our original test was that it used an infobox with only a title, and tried it as either the only infobox on the page or the first one. FandomMobile has special styling for the first infobox on a page - displaying it in large format at the top, and for some reason without the title .

Actually I suspected something along that in the first place and thought my tests ruled it out, but apparently I didn't pay enough attention.

Thank you so much for taking a look again. I've managed to replicate the working example. I've created a "dummy" infobox which is not rendered by the extensions to act as the first infobox, followed by the desired infobox and it seems to be working all through Lua.

I am having trouble getting templates arguments to work using frame:expandTemplate {

title = <template name>,

args = <template args>

}

Inside of the <data><default> tag. The template appears to render but arguments not applied correctly. I haven't looked into it very deeply yet and it's nothing I can't work around but thought I'd call out the odd behavior.

Thanks again!

If you want me to take a look, you'll need to provide a link to the attempt.

I can't seem to recreate it on the dev wiki, but the issue was if the word "Icon" was in the template name (or any template it used), thus giving all templates the Template type: Infoicon. It would display the image, but not the value. I fixed it by renaming the base template to remove "Icon" from the template name. Since I couldn't reproduce it here, I'm not sure why that fixed it, but it sure was difficult to diagnose.

Sounds like an undocumented behavior or something, glad you figured it out.

By the way, next time you can give a link to your original attempts on your wiki, no need to recreate anything on Dev unless there's a specific reason.