Wikipedia:Linter

A linter is software that helps an author or editor of a document (such as a wiki page or a programming file) see if there may be errors in the document. The extension does this for wiki pages: it helps identify whether a page displays as the author intended yesterday in some cases (for example, some image options are "linted" for), and helps identify whether a page displays as the author intended today, due to changes in how the MediaWiki system creates HTML from wikitext. Further reasons can be found at mw:Help:Extension:Linter § Why and what to fix.

From Special:LintErrors

High priority

1. Table tag that should be deleted
2. Misnested tag with different rendering in HTML5 and HTML4
3. Miscellaneous issues
4. Multiline table in list
5. Multiple unclosed formatting tags
6. Paragraph wrapping bug workaround
7. Self-closed tags
8. Old behaviour of link-wrapping font tags
9. Whitespace parsing bug
10. Unclosed quote in heading

Medium priority

1. Bogus file options
2. Fostered content
3. Misnested tags
4. Multi colon escape
5. Links in links

Low priority

1. Missing end tag
2. Missing end tag in heading
3. Obsolete HTML tags
4. Stripped tags

Tracking only

1. Large tables (buggy, not an error; for tracking only; not listed on Special page)
2. Night-mode-unaware-background-color (not an error; for tracking only; not listed on Special page)

Editors (mostly WikiGnomes) are going around Wikipedia working to clean up lint errors, which are sorted by severity into one of three priority levels: high, medium, and low, which relate to how badly the error affects page display, or how much the page display changed when MediaWiki parsing changed. You are welcome to join in this effort. Here are some hints:

• Each lint error page has a help link in the upper-right corner that links to a page with more information about that type of error.
• Lint error pages are sorted approximately in the order of the most recently edited being listed last. Some error pages are sorted better than others.
• Lint error pages are not necessarily complete. When a new lint error type is discovered and a page is made for it, or when the definition of a type of lint error is changed, that lint error page starts empty and is gradually filled by a process that can take several weeks or months.
• Every page's page information details how many errors of each type of lint error that page has. This section is near the end and is omitted if there are no lint errors.
• For each lint error, the count maxes out at 20 in any one page.
• It is
  User and User talk pages, and other people's comments on talk pages; but if you do, please see Wikipedia:Talk page guidelines § Editing others' comments
  for guidance.
  • Don't change the words of other editors.
  • Try to preserve the appearance.
  • It is OK to change the appearance in some cases if it preserves the original intent.
    • It is OK to fix a missing end tag, such as a <small> tag improperly closed with another <small> tag instead of </small>, even if this changes the appearance. This is especially true if the missing end tag affects anything beyond the scope of the comment in which it appears. If a user's comment in the middle of the page causes subsequent comments or sections to be indented wrong, or be bolded or italicized or in a different font, you should insert the missing end tag, even if the page has "always" been wrong.
      • Fixing such errors has become more urgent; after MediaWiki's July 2018 switch to a new linter package, many pages that used to look fine despite errors in them now show terrible appearance and
        accessibility
        problems, such as fonts becoming smaller and smaller (or larger and larger) the further down the page you scroll, due to successive unclosed sizing elements.
    • In a discussion about wiki or HTML markup, unclosed tags are sometimes used. For example, in a discussion about the <div> tag, the tag might not be surrounded by <nowiki> markup, so the <div> tag will be taken as markup with a missing end tag instead of simply displaying the tag. In cases like this, it is helpful to insert <nowiki>...</nowiki> around the unescaped markup, which changes the display, shows the intent of the original comment, and fixes the missing end tag or other errors resulting from the unescaped markup.
  • In a discussion about errors, for example, "Why does the display get messed up when I use [some bad markup]", it's often best to leave the bad markup in place, since otherwise the discussion won't make any sense.
  • Especially on User and User talk pages, try to minimize disruption by getting your fix right on the first try. "Show preview" is your friend.
    • By default, editing a base user talk page will trigger a notification to the user, which can be annoying and should not be done in large batches. To avoid this, use a flagged bot account, and also flag the edit as minor, which will bypass the "You have new messages" notification.
• See also
  WP:HTML 5 § Obsolete elements and attributes for a list of invalid tags and attributes, which you can detect with CSS. See below
  .
• Some Lint errors caused by user signatures and Template substitutions are present across a large number of pages. It is more efficient to fix such errors in a bot task rather than manual edits. You can use
  insource search
  to identify patterns of errors that can be fixed by bots.
• If you find a lint error in an article, consider the possibility that the error was introduced by a recent edit that should be reverted. This is especially true for Table tag that should be deleted and Fostered content lint errors, where careless deletion of table end markup (|}) can cause either of these lint errors. The solution to a lint error may be to revert one or more edits.

• The Firefly Tools table, Outstanding linter errors on enwiki, is a chart with rows for the namespaces and columns for the type of lint error, with each cell in the chart listing the number of errors (maxed at 20 for each error type per article). This chart can help find a project of manageable size, or quickly check the number of lint errors of a certain type in a namespace, such as the Article namespace. This page is updated several times per hour.
• Wikipedia:Linter/reports/Articles by Lint Errors is a report of articles (i.e. pages in the article namespace) that have the most lint errors.
• Wikipedia:Linter/reports/Pages by Lint Errors is a similar report that covers pages in all namespaces. Note that the Linter error system tracks a maximum of 21 errors of any single type, so pages on this list may have more total errors than are shown in the report.
• Wikipedia:Linter/reports/Protected pages by Lint Errors, for protected pages by lint errors

• User:MalnadachBot/Signature submissions

Bots that are approved to run lint fixing tasks:

• User:Legobot (Task 41)
• User:MalnadachBot (Tasks 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12 – blocked as of mid-2023)
• User:Qwerfjkl (bot) (Task 27)
• User:SheepLinterBot (Tasks 1 and 2)
• User:WOSlinkerBot (Tasks 1, 2, 4, 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
• User:WikiCleanerBot (Tasks 7, 10, 17, 22)

User:PerfektesChaos/js/lintHint has instructions for installing and using lintHint, a gadget coded in JavaScript that identifies lint errors in a document in the wiki editor.

You can run lintHint repeatedly in the same edit session to see if you fixed the errors and to relocalize the error pointers. Error pointers are relative to the top of the article, so if you correct errors from the bottom up, you won't need to run lintHint again to relocalize error pointers.

The lintHint tool does not expand relative links when the page is in editing mode. For example, in Portal:Science, {{/Header}} really means {{Portal:Science/Header}}, but lintHint does not do this. To get lintHint to work, you can manually expand relative links. You can also use Expand templates, and enter the page name in Context title and copy part or all of the page into Input wikitext. Then click OK and then press lintHint. Expand templates will often help lintHint localize and identify lint errors listed on Page information but that lintHint doesn't find on its own.

After editing, pages are rechecked for lint errors, usually within seconds, but in the past sometimes delayed for hours. If lintHint says you fixed one or more lint errors, you probably did fix them, even if page information and the specific lint errors page aren't updated yet. As noted, however, lintHint can't detect errors in unexpanded relative links.

You can easily employ

See here for another example.

Other errors

• Wikipedia:Linter/Pages with lint errors that should not be fixed
• Wikipedia:WikiProject Check Wikipedia – project devoted to this and other types of Wikipedia code cleanup
• Category:Pages with syntax highlighting errors (741)
• Possible error: four single quote marks (some might be valid usage denoting a bold phrase inside single quote marks, see
  MOS:SINGLE
  .)

Help pages

• mw:Parsing/Replacing Tidy/FAQ § What will editors need to do? – simplified instructions for fixing pages for the modern MediaWiki parser
• Help:HTML in wikitext
• Wikipedia:HTML5 – information page on technical details of updating WP code to HTML5 + CSS3, including how to replace deprecated HTML 4.01 markup; includes automated searches for obsolete markup
• Wikipedia:Manual of Style/Accessibility
  • Wikipedia:WikiProject Accessibility