#Infobox Builder not loading
67 messages · Page 1 of 1 (latest)
Google Chrome
does refresh fix it?
not at all
@nova basin second time visual builder is reported to stuck on loading in Chrome
I think I'm gonna do some code learning to try manually coding 🤔
I already learned some little tricks like the <div></div> but never go deeper
Thanks, I'm gonna read that
portable infobox is like an element on its own
it starts w/ <infobox> tags
and the rest elements are inside it
try this for lightweght infoboxes:
https://www.mediawiki.org/wiki/Extension:PortableInfobox
you can see the extensions allowed on Miraheze on your
https://YOURNAMEHERE.miraheze.org/wiki/Special:ManageWiki/extensions
I managed to create my infobox with my bare hands I am so proud of myself thanks for your documentations, now I am trying to put an example of utilisation below but I can't display it
try "source code" edit on the infobox
the Visual Editor is another added extension and may lag or fail independently to other extensions
I don't use the visual editor I did everything with the source code
good 👍
I have my Infobox ready and all but I want to have a direct script written below that I can copy to use it on all my pages
something like that
put it between <pre> </pre> tags
Once you have the Infobox, put it on a page of the Template: namespace
For example: Template:Battle
and use {{Battle}} to call the text on that, but you need to do variables
why are you linking MW page? visual builder is part kf extension
last question, does it need line breaks in the <pre> </pre> exemple or not ?
i don't know what is visual builder, and mediawiki is the source wiki for extensions
visual infobox builder is part of portable infobox extension
yowin already successfully enabled extension on his wiki, but builder got bugged
pre stands for pre-formatted so you do need to format it with linebreaks yeah, example would look like
<pre>
stuff
stuff
</pre>
ok. Thanks for explaining visual builder
Okay I got it
But it seems a little, oddly tight on the preview, or that's perfectly normal ?
probably have to put some spaces in there
better I think
oh I thought you meant tight at the = part, since that's usually padded with spaces like there
Oh there can be spaces between words and =
yeah haha
But it still works ?
you can use style stuff for pre blocks, like changing the first <pre> into this for example <pre style="width: fit-content;line-height: 1.5;"> makes the box the width of the content instead of full page and makes the line height bigger (default is 1.3), leading to more vertical space between lines
so line-height would be another way of solving this
the width is optional, just an example of what you can do haha
Jeez I discover a whole new world
And if I want to make it look like it is source code like you do here with your examples I guess there is a specific term to enter
by source code do you mean like you just want it to look like part of the page without the box around it?
No I want it looking like the source code font
oh that's sans serif right? the code in style would be font-family: sans-serif
or maybe the font is monospace actually? 
I think it's monospace yeah
so I need to add <pre style="width: fit-content;line-height: 1.5;font-family:sans-serif"> (or monospace)
yeah
for style the important part is, it needs to be between " " and ; are used to separate entries
Doesn't seems to work it doesn't change anything
can you show the code?
It worked with monospace
Okay it's because it was "sansserif" and not "sans-serif" but Monospace worked better
nice 
Now my last problem is
My example comes in my pages with the infobox when I insert it
I'm sure there is a way to make only the infobox to appear alone without the example below
put it between <noinclude> </noinclude> tags
there are two tags that are really useful for templates, <includeonly> makes things not show up on the template page itself, only showing when the template is inserted elsewhere
and <noinclude> makes things show up on the template page only, and is not inserted onto pages
I just found it on the legroom/infobox page haha
that's the info I wanted, thanks a lot !
Universal Omega and I fixed this on Firefox last year, but I didn't know there was an issue with Chrome
only today saw such complaints, I was suprised too
Yeah it wasn't an issue on Chrome before iirc. Just getting stuck once then worked as usual
I don't have vanilla chrome to test out, both said that refresh doesn't fix it