Template talk:Fake heading

Ungrammatical gibberish

Please remove the ungrammatical "this is fake it is not real" gibberish some random anon IP user added without any discussion. It not only looks ignorant, it messes up existing examples that use this template, by adding extraneous text that is not part of the example and entirely unexpected; it misleads the readers of the examples into thinking that the text "this is fake it is not real" will be part of the actual output! Not acceptable. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 22:39, 24 December 2012 (UTC)

 Done I missed the vandalism before the bit I reverted. --— Gadget850 (Ed) ^talk 00:41, 25 December 2012 (UTC)

Thanks! — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:31, 25 December 2012 (UTC)

Heading 1 to 6

As I document markup, I keep having to use other templates to create examples for other than heading 2 and 3. I have updated {{fake heading/sandbox}} to support heading 1 through 6.

--— Gadget850 (Ed) ^talk 03:09, 20 January 2013 (UTC)

Edit request on 18 May 2013

Level 3 headings use a size of 132%, not 115%. So font-size: 115%; in this template should be changed to font-size: 132%;.

Also, level 4 headings are not the same size as body text, as the /doc says; that’s level 5. 4 have a size of 116% (which is also not 115%). Frungi (talk) 00:56, 18 May 2013 (UTC)

Missing subheading levels

Is there a reason this template does not support level 4–6 subheadings? I know the /doc says they’re seldom used, but that’s no reason to intentionally make them unavailable here; you have to assume that if someone wants to use sub=6, he has a reason. —Frungi (talk) 01:22, 18 May 2013 (UTC)

And less than an hour later, this is moot because it does now, thanks to User:Gadget850. —Frungi (talk) 02:16, 18 May 2013 (UTC)

Per above, I made updates months ago and started a discussion, with no response. This has been on my long todo list. And I do update documentation. --  Gadget850 ^talk 02:24, 18 May 2013 (UTC)

Edit request on 25 May 2013

A couple of sizes used in this template are not the sizes I see in actual headings. Using the Vector skin with no custom CSS, <h1> is sized at 1.6em rather than a percentage; <h5> has a size of 105%, not 100%; and <h6> is sized at 100%, same as body text. This could be fixed by replacing the following lines:

| 1 = font-size: 1.6em; margin-bottom: .6em; border-bottom: 1px solid #aaa;

| 5 = font-size: 105%; font-weight: bold; margin-bottom: .3em;
| 6 = font-size: 100%; font-weight: bold;

Frungi (talk) 08:18, 25 May 2013 (UTC)

Both the Vector and the Monobook stylesheets contain:

h1, h2, h3, h4, h5, h6 {
		font-weight: bold;
	}

h2, h3, h4, h5, h6 {
		page-break-after: avoid;

/* Structural Elements */
	h1,
	h2,
	h3,
	h4,
	h5,
	h6 {
		color: black;
		background: none;
		font-weight: normal;
		margin: 0;
		overflow: hidden;
		padding-top: .5em;
		padding-bottom: .17em;
		border-bottom: 1px solid #aaa;
	}
	h1 {
		font-size: 188%;
	}

	h2 {
		font-size: 150%;
	}

	h3,
	h4,
	h5,
	h6 {
		border-bottom: none;
		font-weight: bold;
	}
	h3 {
		font-size: 132%;
	}

	h4 {
		font-size: 116%;
	}
	


	h5 {
		font-size: 105%;
	}


	h6 {
		font-size: 100%;
	}


	
	/* Some space under the headers in the content area */
	h1,
	h2 {
		margin-bottom: .6em;
	}
	h3,
	h4,
	h5 {
		margin-bottom: .3em;
	}

A little hard to interpret as it sets and resets stuff.

Wikimarkup	HTML	Style
= Heading =	<h1>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 1.8em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;
== Heading ==	<h2>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 1.5em; font-family: Georgia,Times,serif; margin-top: 1em; margin-bottom: 0.25em; line-height: 1.3; padding: 0; border-bottom: 1px solid #AAAAAA;
=== Heading ===	<h3>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 1.17em; font-weight: bold; margin-top: 0.3em; margin-bottom: 0; line-height: 1.6; padding-top: 0.5em; padding-bottom: 0;
==== Heading ====	<h4>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 100%; font-weight: bold; margin-top: 0.3em; margin-bottom: 0; line-height: 1.6; padding-top: 0.5em; padding-bottom: 0;
===== Heading =====	<h5>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 100%; font-weight: bold; margin-top: 0.3em; margin-bottom: 0; line-height: 1.6; padding-top: 0.5em; padding-bottom: 0;
====== Heading ======	<h6>	color: #000000; background: none; overflow: hidden; page-break-after: avoid; font-size: 100%; font-weight: bold; margin-top: 0.3em; margin-bottom: 0; line-height: 1.6; padding-top: 0.5em; padding-bottom: 0;

So, h5 and h6 sizes need to be updated, but h1 is correct. Don't know if this is a change or I just made a mistake.--  Gadget850 ^talk 10:51, 25 May 2013 (UTC)

All true, but the <h1> font-size is overridden by

	#firstHeading {
		padding-top: 0;
		margin-top: 0;
		font-size: 1.6em;
	}

—Frungi (talk) 11:15, 25 May 2013 (UTC)

Then again, is there a need for a first-level heading? Could the template just drop that one? —Frungi (talk) 11:22, 25 May 2013 (UTC)

Missed that. Of course, it is only when used by the MediaWiki software as the first heading; used elsewhere (where it shouldn't) it is 188%. Removed h1 and updated h5 and h6.

When I originally created this, the idea was that the headings would must not be exactly the same as real headings, just similar enough to get the point across. They need to be smaller, and should not ever be confused with the real thing. Also, if this font choices that typography makeover or whatever their calling it are being done somewhere with a class, this template should use it, too. The complaints about the serif heads are piling up and its very likely they're going to be done away with.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:32, 30 April 2014 (UTC)

Why did you remove level 1? It happens that one wants to fake that, probably more often than level 5 or 6. {{fake title}} even redirects here. — Christoph Päper 10:22, 25 June 2014 (UTC)

Note: Adding level 1 back isn't as simple as pasting in the previous template code, as in the intervening time the styles have changed due to mw:Typography refresh. — Mr. Stradivarius ^{♪ talk ♪} 16:23, 3 July 2014 (UTC)

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Lots of good discussion here, but I don't see any consensus that a  Template editor could act on at this time. — {{U|Technical 13}} ^{(e • t • c)} 22:12, 4 July 2014 (UTC)

Edit request: new param "anchor"

Proposing the addition of new named param "anchor" (could also be positional param 2). If "anchor" is present and set to "1" (or "yes" or "true") then the value of the unnamed param (param 1) in the {{fake header}} invocation is used as the value of the unnamed param in an {{anchor}} template, to be generated in front of the fake header.

Reason: Sometimes I want my fake heading to be link-addressable, that is, have an anchor associated with it that can be the target of a wikilink from the same page or other pages.

Example: {{fake heading|sub=3|Heading three|anchor=yes}} would generate the equivalent of:

{{Anchor|Heading three}}{{fake heading|sub=3|Heading three}}

This still avoids ToC clutter, but provides wikilink addressability. Mathglot (talk) 12:09, 4 February 2018 (UTC)

 Not done for now: Please put proposed code on template sandbox and get show consensus (or at least lack of opposition) for this change — Martin (MSGJ · talk) 07:47, 5 February 2018 (UTC)

Will do, thank you. (Might not be right away.) Mathglot (talk) 04:48, 6 February 2018 (UTC)

Using this in articles? Does it comply with the MOS in article space?

Does the use of this template comply with MOS:GOODHEAD and WP:PSEUDOHEAD?

In this diff an editor removed the normal headers to use this template. Is this the intended use of this template? Is the use of this template supposed to ever happen in article space? I assume based on the above conversation that this template also doesn't support anchors, is that accurate? If not, I don't think it complies with the above MOS guidelines and I think it should be made clear that this template should not be used in articles. Thanks, - Paul^T+/_C 16:54, 18 April 2018 (UTC)

This template does not comply with WP:PSEUDOHEAD. The editors who use this are trying to force their own style without getting consensus on WT:MOS. Bright☀

Editprotected

Could the TFD notice be noincluded? Lojbanist ^{remove cattle from stage} 05:08, 5 May 2018 (UTC)

I'll note that a more customary way of hiding the TFD notice in articles, according to the template documentation, is to change the |type= parameter of {{Template for discussion/dated}} from "inline" to "disabled". Mz7 (talk) 01:59, 6 May 2018 (UTC)

TfD tags for this kind of large, non-inline template should not be noincluded. In fact, |type=inline is itself a bad attempt to reduce the prominence of the tag. No. {{3x|p}}ery (talk) 23:27, 6 May 2018 (UTC)

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. — Martin (MSGJ · talk) 10:32, 8 May 2018 (UTC)

Workaround needed

Over at MediaWiki#Markup there is a need to show readers what a level four heading looks like, without that heading appearing in the TOC. After the recent bot edit, readers are seeing a bunch of equals signs. Adding a newline before the heading will make the heading appear, but will also make it appear in the TOC. Any suggestions? -- John of Reading (talk) 15:00, 10 May 2018 (UTC)

Template-protected edit request on 11 May 2018

Please add Category:Pages with templates in the wrong namespace after {{error|Per [[WP:PSEUDOHEADING]] this template should not be used in articles.}}. {{3x|p}}ery (talk) 19:07, 11 May 2018 (UTC)

 Done — JJMC89 (T·C) 04:47, 12 May 2018 (UTC)

Integrate TemplateStyles

I created a TemplateStyles page for this, and the styles works pretty while, so I hope it would be approved soon. Great Brightstar (talk) 18:15, 6 December 2018 (UTC)

If you approve it, you can just get the new source code from sandbox. Great Brightstar (talk) 18:18, 6 December 2018 (UTC)

 Not done: Your changes do more than just change to using TemplateStyles. You've also removed the errorchecking which ensures that the template is not used in articles.

I also fail to see any benefit to this change. Splitting out the style to a css page is useful if there's a family of templates that should be kept in line with each other. Here, there's just one template. What's the point? Cabayi (talk) 20:38, 9 December 2018 (UTC)

I added errorchecking back in sandbox page. --Great Brightstar (talk) 08:41, 11 December 2018 (UTC)

Well, in this this page I saw this template is used multiple times, so I think it's resonable to convert inline styles to TemplateStyles. --Great Brightstar (talk) 14:21, 5 April 2019 (UTC)

 Not done Agree with Cabayi here; there is no need to split this into a CSS page. {{3x|p}}ery (talk) 22:21, 5 April 2019 (UTC)

Template-protected edit request on 24 October 2021 by DesertPipeline

This template's appearance doesn't match that of real headings on systems without Microsoft fonts. This can be fixed by adding 'Linux Libertine', after the two instances of font-family: in the template. Regards, DesertPipeline (talk) 20:54, 24 October 2021 (UTC)

 Done User:GKFX^talk 18:35, 25 October 2021 (UTC)

Thanks :) It renders properly now. DesertPipeline (talk) 21:17, 25 October 2021 (UTC)

Add a class

Please, add a class="fake-heading" (for example) to the template to allow customization for the unnecessarily amended font. Thanks. --Mahmudmasri (talk) 21:53, 14 February 2022 (UTC)

Edit request to complete TfD nomination

Template:Fake heading has been listed at Templates for discussion (nomination), but it was protected, so it could not be tagged. Please add:

{{subst:template for discussion|help=off}}

to the top of the page to complete the nomination. Thank you. Frostly (talk) 03:23, 1 July 2023 (UTC)

 Completed. P.I. Ellsworth , ed. ^{put'er there} 09:24, 1 July 2023 (UTC)