Sorry about that, I have fixed it.
You can find scripts deleted during the latest UCP cleanup in the content-review-lookup repository, updated weekly, with all sitewide JS on Fandom. That script's latest revision specifically can be found here.
Yes. Also, AbuseFilter still doesn't work with Discussions. But anyways, the user was able to post on Discussions since so I assume this problem has been resolved.
Are you able to edit your userpage?
One approach would be:
<p style="line-height: 16px;">'''{{{Original Japanese}}}'''<br/><small>{{{Romaji/hepburn}}}</small><br><small>(''{{{English}}}'') </small> {{{Text}}}</p>
but in that case you would have to specify a Text parameter to the template with the text that displays after the English translation. If you instead place that text after the template, it'll end up below the intro paragraph. This isn't ideal, because your whole intro paragraph would be a template.
Sure, here's what it looks like in Visual Editor source mode's preview in incognito mode:
I'm using PseudoMonobook with Dark Reader on a 1980x1080 screen, which is why the contents of the screenshot may look off, but that's how I interpreted their "after the bracket of the English translation". Also, because I happened to look through the Getting Technical board today.
If this is what you want it to look like:
then it's just the same template you currently use but without <div style="float:left;"> and </div>.
I disabled the script from running on the UCP because Staff said it was causing issues. I believe it was causing issues when I ran it back then, but either way, WAM is not on the UCP yet.
content-disposition: inline; filename="Toriel_battle.webp"; filename*=UTF-8''Toriel_battle.webp content-type: image/webpwhereas on here I'm seeing
content-disposition: inline; filename="Toriel_battle.png"; filename*=UTF-8''Toriel_battle.png content-type: image/pngin the response headers for these images. Using a different domain (
images.wikia.nocookie.net
or images.wikia.com
) also does not change these headers.
Content-Disposition
header (that Chrome is for some reason ignoring and just downloading them as PNG) when accessed without ?format=original
but that these images have quality losses.
</p>