Template talk:Br: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 10: Line 10:
::::The idea is, if the <nowiki><br clear=all></nowiki> is preceding the navigation templates, it should be replaced with {{tem|BoxTop}}, otherwise you can safely replace it with {{tem|br}}. But I think it's not worth it to mass edit all articles for such a minor change, instead, if you come by it while regularly editing, you can then replace it.--{{User:Megadardery/sig}} 15:05, 19 January 2016 (EST)
::::The idea is, if the <nowiki><br clear=all></nowiki> is preceding the navigation templates, it should be replaced with {{tem|BoxTop}}, otherwise you can safely replace it with {{tem|br}}. But I think it's not worth it to mass edit all articles for such a minor change, instead, if you come by it while regularly editing, you can then replace it.--{{User:Megadardery/sig}} 15:05, 19 January 2016 (EST)
:::::Yeah, exactly what Megadardery said. Also keep in mind that it can be replaced with <nowiki>{{br|left}} or {{br|right}}</nowiki> when it seems appropriate: it often leads to neater-looking pages than just automatically clearing everything every time. - {{User:Walkazo/sig}} 15:59, 19 January 2016 (EST)
:::::Yeah, exactly what Megadardery said. Also keep in mind that it can be replaced with <nowiki>{{br|left}} or {{br|right}}</nowiki> when it seems appropriate: it often leads to neater-looking pages than just automatically clearing everything every time. - {{User:Walkazo/sig}} 15:59, 19 January 2016 (EST)
::::::We could mass edit if moderators could do a RegExp search and replace or something but I can agree that regular editing instead of seeking edits to be made to replace <nowiki><br clear=all></nowiki> with {{tem|br}} is a good idea to keep in mind. --{{User:Wildgoosespeeder/sig}} 16:18, 19 January 2016 (EST)

Revision as of 16:18, January 19, 2016

Usage

The template seems to be used in only two pages (check what links here). Shouldn't the template be used in articles...? RAP.pngRAP... *blink blink* 2 pages...

Replace?

Question.svg This talk page or section has a conflict or question that needs to be answered. Please try to help and resolve the issue by leaving a comment.

I see a lot of <br clear=all>. Should it be replaced with {{br}}? --Wildgoosespeeder (talk) (Stats - Contribs) 02:42, 18 January 2016 (EST)

They're perfectly interchangeable, or at least so I believe. I think there's no point in changing all instances of <br clear=all>, both function the same. --TucayoSig.png The 'Shroom 17:27, 18 January 2016 (EST)
Wouldn't it make editing pages easier? Also if there is a problem with the source code of {{br}} or the raw code <br clear=all>, all pages that use the template will be corrected automatically. --Wildgoosespeeder (talk) (Stats - Contribs) 17:43, 18 January 2016 (EST)
Besides that having it in the template is easier maintenance as said, using clear=all on a BR is obsolete with HTML5. This template uses the correct coding, in addition to not even using a BR. Lakituthequick.png Lakituthequick 14:40, 19 January 2016 (EST)
The idea is, if the <br clear=all> is preceding the navigation templates, it should be replaced with {{BoxTop}}, otherwise you can safely replace it with {{br}}. But I think it's not worth it to mass edit all articles for such a minor change, instead, if you come by it while regularly editing, you can then replace it.--
User:MegadarderyUser talk:MegadarderyDashbot signature
15:05, 19 January 2016 (EST)
Yeah, exactly what Megadardery said. Also keep in mind that it can be replaced with {{br|left}} or {{br|right}} when it seems appropriate: it often leads to neater-looking pages than just automatically clearing everything every time. - Walkazo 15:59, 19 January 2016 (EST)
We could mass edit if moderators could do a RegExp search and replace or something but I can agree that regular editing instead of seeking edits to be made to replace <br clear=all> with {{br}} is a good idea to keep in mind. --Wildgoosespeeder (talk) (Stats - Contribs) 16:18, 19 January 2016 (EST)