User talk:Qwertyuiopfromdefly

Explain xkcd: It's 'cause you're dumb.
Revision as of 09:33, 2 April 2026 by 82.132.237.40 (talk) (Questions (answered?))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

:D Qwertyuiopfromdefly (talk) 06:05, 17 February 2026 (UTC)

What the little thingys in the Userbox mean

If I'm correctly assuming what you're confused about, you're wondering what 'border-c', 'border-s', 'info-s', and 'info-c' parameters do. Let's go through them:

  • border-c - Determines the color of the userbox's border. But a hex color value here to change the color of the border. if not included, defaults to grey.
  • border-s - Determines the width of the border in pixels. A higher value means a thicker border, while a lower value means a thinner one. If not included, it defaults to 1 pixel.
  • id-s - Determines the size of the id text in points. A higher value means a bigger font size, and a lower value means a smaller font size. If not included, it defaults to your system's default font size+2.
  • info-s - Determines the size of the info text in points. Increase this value for a bigger font size, and decrease it for a smaller font size. If not included, defaults to your system's default font size.
  • info-c - The background color for the 'info' section of the user box. Change this value for a different background text color. if not included, defaults to a darker grey.
  • Float - Where the userbox goes. Can be left, center, or right.
  • Align - Determines whether the text is left, center, or right aligned. If not included, text defaults to left aligned

Hope this helps! I'll update this list later with more parameters. --DollarStoreBa'alConverse (BLM) 15:07, 18 February 2026 (UTC)

Thank you! Qwertyuiopfromdefly (talk) 20:08, 18 February 2026 (UTC)
I also found id-c while messing around Qwertyuiopfromdefly (talk) 20:16, 18 February 2026 (UTC)
That one sets the background color for the id section rather than the info section. Also, I made a mistake. It's 'float'. 'Align' is a different command (which I've now added to the list above). --DollarStoreBa'alConverse (BLM) 20:19, 18 February 2026 (UTC)
LOL I love the changes you've made to your userboxes btw. --DollarStoreBa'alConverse (BLM) 20:19, 18 February 2026 (UTC)
Thank you Qwertyuiopfromdefly (talk) 20:22, 18 February 2026 (UTC)

Questions (answered?)

how do you create subpages -- copied from User:Qwertyuiopfromdefly, by user.

The same way you create any new page... As soon as you can create pages.
Or ask someone else (speicifcally, or in a general request) who can create pages to create the for you.
But I'd suggest that you (or anyone other person who wants to help you) only does so if you're sure there's a good reason for it. There's a tendency for new (sub-)pages to be created far more readily than anything that's no longer wanted is to be tidied away by deletion again.
So, perhaps you could say what you want to create, for two main reasons:
  1. It might get someone to help you out (or tell you exactly what to do to help yourself out),
  2. If it's frivilous, someone can tell you that, maybe point out that there's a better way (like using an established Sandbox page, or something).
Sorry for a lot of words to such a short 'question', it's just because it is so short, so I'm imagining all kinds of (good and bad) reasons behind it and trying to cover all the obvious bases. ;) 81.179.199.253 20:05, 8 March 2026 (UTC)
Thank you, I was just curious and don't have any plans to make any subpages yet. Qwertyuiopfromdefly (talk) 23:55, 8 March 2026 (UTC)

why is there a </div> underneath the discussion on the main page? -- copied from User:Qwertyuiopfromdefly, by user

Somewhere, this is an unbalanced set of tags. At least at one point, someone's signature had a strange imbalance in the <​span> tags they used that may have created a closing </div> to have become visible in certain circumstances. Though it was never quite so clear how, it seemed to vanish when that issue was corrected, and was only visible when viewing the Comic page which transcluded its Talk page (by way of the {{comic discussion}} template), but not when viewing the Talk page directly.
The main page, in turn, transcludes the Latest Comic page into it, using {{:{{LATESTCOMIC}}}}, but the {{comic discussion}} actually is specifically coded to not show the Discussion (i.e. Talk page) when it would ultimately be doubly-transcluded into the Main Page (the Main page instead has some code to provide a dynamic replacement link to the current newest comic's Discussion/Talk page, to discourage comments about it going on the Main page's Talk page... if you follow me). Theoretically, the exact same error should not occur, but you can see that a similar "in a grey box" method is being used to show where the transcluded Talk sits in the Comic page it relates to, and the Comic (sans Talk) sits in the Main page.
It's really not obvious what exactly is wrong here, though. The tags (in particular the <div>...</div> segment of the Main page's 'insert Latest Comic page here' bit, plus the nested <span>...</span>s within it) seem to be balanced and properly nested, at first view. But a combination of the various source page 'wikimarkup's (as editable by us, which contain such HTML tags as well as 'wikitags') and the way that the wiki's background code scrunches all that up (like shoving templates and other transclusions into the 'outer" page, and translating wikimarkup into its HTML markup equivalent) so that the browser displays the intended content+style... Well, it seems to have produced a 'spare' DIV-ending that ends up being rendered literally.
I'm wondering if the ultimate culprit is the --></div>__NOTOC__}} that is the very last line of the comic discussion template. It should close-DIV only if it isn't in the Main page (from the initial {{#ifeq:{{FULLPAGENAME}}|{{MediaWiki:mainpage}}| check), and it should probably pair up to the <nowikiíclass="disctemp"</nowiki> open-DIV, part way down, if (and only if) it isn't entirely excluded by the #ifeq checking (and the two other "is the Talk page existing+non-empty" layers of check are entirely within that DIV-pair), but it needs proper checking to make sure no odd circumstances and potentially misbalanced tags and/or {{}}s exist.
Because the Main page and the Comic Discussion template are both (semi-/fully-)protected, a humble IP such as myself cannot do the troubleshooting that I might do. (e.g., add some temporary plaintext either side of the template's closing DIV, and see if/where that shows up within the various key pages that ultimately may contain that close-tag). But that's probably what I'd do first. If it's working as it looks like it should do, no error in the Comic Talk page (e.g., yet another signature markup error) would ever make it 'out' onto the Main front page. Having (probably) ruled this out as the offending overflowing close-tag, and reverted any temporary edits, I could then look at the Comic page's other contents with more confidence, and then (after ruling all that out, assuming I could) someone with Main Page editing rights temporarily adding extra debug-plaintext around that page's various DIV-openers/-closers. If that still doesn't help identify it, then the page-source (HTML, via browser) needs thorough checking, looking for how the various nested wikikarkup (including implicit/explicit HTML tagging) gets rendered out that way at the browser layer. But I'd hope it didn't have to come to that.
There is one quick test I could do, myself, right now, though... Might just do it. But (as it currently stands, assuming I don't edit again shortly) this is by way of a 'brief' explanation as to possible reasons that I can't really confirm right now. But that I consider plausible. 82.132.237.40 09:33, 2 April 2026 (UTC)