If you are using {{DISPLAYTITLE}} to format a page name to have a leading lower case character (or really any formatting at all) the {{PAGENAME}} does not obey the display rule.
I think this is a bug.
47.186.29.164 47.186.29.164 01:12, 14 October 2023 (UTC)Reply
{{PAGENAME}} is used to get the page title for further processing (finding a subpage with the same name, its root page, using it in a conditional expression etc.). In these cases, any formatting is more harmful than useful. In addition, what if the wikitext fragment containing {{PAGENAME}} is processed before the wikitext fragment containing {{DISPLAYTITLE:…}}? It would lead to inconsistent results. —Tacsipacsi (talk) 13:39, 15 October 2023 (UTC)Reply
{{READOUTTITLE}}" ... but let me guess that some could object this idea, since it could be abused as a replacement for the malicious Extension:Variables. Taylor 49 (talk) 14:58, 17 March 2024 (UTC)Reply
I suggest that the magic word "{{TRANSCLUSIONCOUNT}}" can be added, I'm sure it's quite expensive, what that function does is display the amount of transclusions it makes to itself, return 0 if is displayed on the source page, but return 1 if displayed from a page that transcludes the source page, return 2 if displayed from the page that transcludes the previous one, and so on, so it is possible to use it with "{{#ifexpr}}" to mainly prevent the main template containing that magic word from being transcluded a certain number of times 95.143.193.15 19:43, 4 October 2024 (UTC)Reply
The tables on this page appear to have recently been wrapped in class="noresize". I'm not entirely sure what the goal of doing this is (I imagine it's some kind of mobile support, although no information was provided in the edit summaries), but on Firefox on desktop it causes the tables to be enclosed in divs with scrollbars, with a pointless large block of space underneath them. It makes scrolling through this page substantially more inconvenient. I will revert this change, but if @Jdlrobson could explain what the purpose of these changes are, perhaps there is a way to apply the desired functionality without breaking the page on Firefox. SnorlaxMonster (talk) 06:12, 19 October 2024 (UTC)Reply
fullurl, canonicalurl, etc. dont produce mobile view links while clicking them on mobile. is there a method to match output to the domain? if viewing on xx.m.yy.org the link should be the same and not xx.yy.org . RoyZuo (talk) 13:20, 29 November 2024 (UTC)Reply
/wiki/….) By the way, the whole mobile domain thing is a big hack – ideally, we’d have software that works greatly on small and large screens, with keyboard, mouse and touchscreen, and we wouldn’t have a separate mobile domain at all. But we’re far from that. —Tacsipacsi (talk) 22:04, 30 November 2024 (UTC)Reply
{{WBREPONAME}} and possibly many other Magic words are not mentioned here. For example, en:MediaWiki:Exceeded-entity-limit-category reads Pages with too many {{WBREPONAME}} entities accessed. {{WBREPONAME}} produces Wikidata. Even though these magic words might not be widely used, I think all of them should be properly documented here. —CX Zoom (A/अ/অ) (let's talk|contribs) 20:15, 6 January 2025 (UTC)Reply
I can use
{{#tag:syntaxhighlight|<b>test code</b>|lang="wikitext"}}
to render a syntaxhighlight tag like this:
How can I use the same syntax to include the "inline" attribute, which takes no parameter value? Jonesey95 (talk) 00:50, 21 March 2025 (UTC)Reply
inline="" works, because it is created by Visual Editor. Looks like inline= works too, but I'm not sure it's always the case. IKhitron (talk) 11:50, 21 March 2025 (UTC)Reply
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4