Knowledge

:Linter - Knowledge

Source 📝

95: 35: 377:, 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. 515:, 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. 1054:
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,
1015:
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.
313:, 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: 323:
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
135:
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
114:
that aims to identify "lint": syntax errors in the code of Knowledge pages. The lint in this case is broken and problematic markup on all wiki pages that cannot be fixed automatically by MediaWiki. The extension produces a list of these errors at
771: 527:
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
454:
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
418:
In a discussion about errors, for example, "Why does the display get messed up when I use ", it's often best to leave the bad markup in place, since otherwise the discussion won't make any sense.
413:
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.
1127: 1145: 119:, which editors and bots can consult to find pages that need attention. High-priority Linter issues require fixing as they may cause pages to display in undesirable fashion. 1110: 466:
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
281: 531: 985: 981: 977: 842: 838: 192: 973: 867: 387:
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.
952: 948: 944: 940: 936: 932: 928: 924: 920: 916: 912: 817: 813: 809: 266: 908: 904: 900: 896: 892: 863: 805: 801: 797: 793: 789: 785: 781: 383:; 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 888: 777: 320:
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.
1051:. Expand templates will often help lintHint localize and identify lint errors listed on Page information but that lintHint doesn't find on its own. 187: 182: 58:; rather, its purpose is to explain certain aspects of Knowledge's norms, customs, technicalities, or practices. It may reflect differing levels of 518: 756: 432:
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
217: 1138: 524: 1163: 331:
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.
350: 43: 408:
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
197: 140:
in some cases (for example, some image options are "linted" for), and helps identify whether a page displays as the author intended
317:
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.
249: 229: 212: 172: 1184: 244: 544: 467: 712: 700: 688: 676: 664: 652: 640: 293: 1132: 628: 616: 604: 592: 485:
without there actually being any errors on the pages themselves. If there's nothing obviously wrong with a listed page, and
177: 1206: 261: 202: 1189: 149: 239: 207: 497:
show no errors, it will often disappear from the list on its own after a while. Editors can usually expedite this by
55: 512: 444: 392:
In a discussion about wiki or HTML markup, unclosed tags are sometimes used. For example, in a discussion about the
276: 271: 1031:, but lintHint does not do this. To get lintHint to work, you can manually expand relative links. You can also use 1001: 421:
Especially on User and User talk pages, try to minimize disruption by getting your fix right on the first try. "
1211: 1096: 1072: 51: 17: 1181:+ CSS3, including how to replace deprecated HTML 4.01 markup; includes automated searches for obsolete markup 63: 234: 478:) can cause either of these lint errors. The solution to a lint error may be to revert one or more edits. 471: 996: 580: 550: 1092: 120: 1019:
The lintHint tool does not expand relative links when the page is in editing mode. For example, in
1032: 494: 1106:
This CSS only detects no-longer-valid markup; it has no means of detecting other coding errors.
1169: 521:
is a report of articles (i.e. pages in the article namespace) that have the most lint errors.
486: 328: 223: 1091:– turn pink so it sticks out like a sore thumb. You can customize as you like for your own 106: 8: 1068: 962: 852: 827: 306: 111: 59: 1058: 287: 166: 81: 1064: 498: 482: 456: 429: 338: 310: 161: 116: 73: 255: 1103:(transclude) lint.css directly into your own user CSS at this or any other WMF wiki. 877: 857: 766: 422: 362:
It is OK to change the appearance in some cases if it preserves the original intent.
399: 1005: 1174: 1149:(some might be valid usage denoting a bold phrase inside single quote marks, see 433: 346: 132: 99: 155: 1020: 882: 342: 538: 1200: 1067:
to detect a lot of "linty" old HTML 4 code in pages as you read, if you're a
832: 1121: 751: 746: 1166:– simplified instructions for fixing pages for the modern MediaWiki parser 447:
for a list of invalid tags and attributes, which you can detect with CSS.
300: 1075:
for a sample CSS declaration that makes various deprecated cruft – like
1157: 1150: 1009: 967: 460: 384: 349:, and other people's comments on talk pages; but if you do, please see 296:(buggy, not an error; for tracking only; not listed on Special page) 1135:– project devoted to this and other types of Knowledge code cleanup 94: 1128:
Knowledge:Linter/Pages with lint errors that should not be fixed
1177:– information page on technical details of updating WP code to 334:
For each lint error, the count maxes out at 20 in any one page.
1012:
that identifies lint errors in a document in the wiki editor.
126: 1178: 1164:
mw:Parsing/Replacing Tidy/FAQ § What will editors need to do?
436:, which will bypass the "You have new messages" notification. 1055:
lintHint can't detect errors in unexpanded relative links.
145: 1116: 474:
lint errors, where careless deletion of table end markup (
463:
to identify patterns of errors that can be fixed by bots.
428:
By default, editing a base user talk page will trigger a
351:
Knowledge:Talk page guidelines § Editing others' comments
178:
Misnested tag with different rendering in HTML5 and HTML4
505: 532:
Knowledge:Linter/reports/Protected pages by Lint Errors
1004:
has instructions for installing and using lintHint, a
144:, due to changes in how the MediaWiki system creates 490: 719: 724:Bots that are approved to run lint fixing tasks: 309:) are going around Knowledge working to clean up 1198: 519:Knowledge:Linter/reports/Articles by Lint Errors 148:from wikitext. Further reasons can be found at 1139:Category:Pages with syntax highlighting errors 150:mw:Help:Extension:Linter § Why and what to fix 525:Knowledge:Linter/reports/Pages by Lint Errors 365:It is OK to fix a missing end tag, such as a 1099:, or follow the instructions at lint.css to 448: 445:WP:HTML 5 § Obsolete elements and attributes 123:describes 18 specific types of lint errors. 381:Fixing such errors has become more urgent 396:tag, the tag might not be surrounded by 356:Don't change the words of other editors. 208:Old behaviour of link-wrapping font tags 93: 1185:Knowledge:Manual of Style/Accessibility 1146:Possible error: four single quote marks 14: 1199: 1039:and copy part or all of the page into 545:Knowledge:Linter/Signature submissions 1133:Knowledge:WikiProject Check Knowledge 481:Occasionally, large pages show up on 534:, for protected pages by lint errors 29: 1190:Knowledge:WikiProject Accessibility 513:Outstanding linter errors on enwiki 369:tag improperly closed with another 282:Night-mode-unaware-background-color 24: 56:Knowledge's policies or guidelines 25: 1223: 741:Lint fixes status (last 30 days) 198:Paragraph wrapping bug workaround 193:Multiple unclosed formatting tags 468:Table tag that should be deleted 173:Table tag that should be deleted 33: 1002:User:PerfektesChaos/js/lintHint 359:Try to preserve the appearance. 1097:meta:Special:MyPage/global.css 1073:meta:User:SMcCandlish/lint.css 997:User Javascript tool: lintHint 557:Linter error count progression 551:Linter error count progression 13: 1: 1071:who likes to do cleanup. See 1035:, and enter the page name in 121:The MediaWiki wiki help page 7: 1207:Knowledge information pages 10: 1228: 566:Outstanding linter errors 267:Missing end tag in heading 71: 27:Knowledge information page 1093:Special:MyPage/common.css 1029:{{Portal:Science/Header}} 961: 876: 851: 826: 765: 745: 740: 737: 734: 731: 568: 565: 562: 511:The Firefly Tools table, 218:Unclosed quote in heading 1059:User CSS tool: lint.css 822:Blocked as of mid-2023 188:Multiline table in list 1063:You can easily employ 772:User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ 213:Whitespace parsing bug 102: 1212:Knowledge maintenance 1170:Help:HTML in wikitext 1113:for another example. 501:the page in question. 97: 183:Miscellaneous issues 107:The Linter extension 52:encyclopedic article 963:User:WikiCleanerBot 853:User:SheepLinterBot 828:User:Qwerfjkl (bot) 728: 559: 411:...</nowiki: --> 156:List of lint errors 112:MediaWiki extension 727: 555: 539:Other useful pages 495:template expansion 425:" is your friend. 382: 272:Obsolete HTML tags 245:Multi colon escape 230:Bogus file options 162:Special:LintErrors 117:Special:LintErrors 103: 994: 993: 878:User:WOSlinkerBot 858:User:Sheep8144402 767:User:MalnadachBot 717: 716: 380: 92: 91: 16:(Redirected from 1219: 1148: 1102: 1090: 1086: 1082: 1078: 1050: 1046: 1042: 1038: 1033:Expand templates 1030: 1026: 729: 726: 706:28 December 2023 670:23 February 2023 658:13 February 2023 560: 558: 554: 487:page information 483:lint error lists 477: 472:Fostered content 412: 407: 403: 395: 376: 372: 368: 329:page information 305:Editors (mostly 301:How you can help 235:Fostered content 203:Self-closed tags 98:Cleaning up the 84: 44:information page 37: 36: 30: 21: 1227: 1226: 1222: 1221: 1220: 1218: 1217: 1216: 1197: 1196: 1175:Knowledge:HTML5 1160: 1144: 1124: 1119: 1100: 1089:<strike: --> 1088: 1085:<center: --> 1084: 1080: 1076: 1061: 1048: 1047:and then press 1044: 1040: 1036: 1028: 1024: 999: 722: 646:4 February 2023 634:3 November 2022 556: 553: 541: 508: 475: 461:insource search 410:<nowiki: --> 409: 405: 404:markup, so the 397: 393: 375:</small: --> 374: 373:tag instead of 370: 366: 341:other people's 303: 290: 262:Missing end tag 258: 226: 224:Medium priority 169: 158: 129: 88: 87: 80: 76: 68: 67: 34: 28: 23: 22: 15: 12: 11: 5: 1225: 1215: 1214: 1209: 1195: 1194: 1193: 1192: 1182: 1172: 1167: 1159: 1156: 1155: 1154: 1142: 1136: 1130: 1123: 1120: 1118: 1115: 1060: 1057: 1041:Input wikitext 1021:Portal:Science 998: 995: 992: 991: 988: 970: 965: 959: 958: 955: 885: 883:User:WOSlinker 880: 874: 873: 870: 860: 855: 849: 848: 845: 835: 830: 824: 823: 820: 774: 769: 763: 762: 759: 754: 749: 743: 742: 739: 736: 733: 721: 718: 715: 714: 710: 707: 703: 702: 698: 695: 691: 690: 686: 683: 679: 678: 674: 671: 667: 666: 662: 659: 655: 654: 650: 647: 643: 642: 638: 635: 631: 630: 626: 623: 619: 618: 614: 611: 607: 606: 602: 599: 595: 594: 590: 587: 583: 582: 578: 575: 574:28 August 2018 571: 570: 567: 564: 552: 549: 548: 547: 540: 537: 536: 535: 529: 522: 516: 507: 504: 503: 502: 479: 464: 452: 441: 440: 439: 438: 437: 419: 416: 415: 414: 390: 389: 388: 371:<small: --> 367:<small: --> 360: 357: 353:for guidance. 335: 332: 325: 321: 318: 302: 299: 298: 297: 289: 286: 285: 284: 279: 274: 269: 264: 257: 254: 253: 252: 250:Links in links 247: 242: 240:Misnested tags 237: 232: 225: 222: 221: 220: 215: 210: 205: 200: 195: 190: 185: 180: 175: 168: 165: 157: 154: 143: 139: 128: 125: 90: 89: 86: 85: 77: 72: 69: 49: 48: 40: 38: 26: 18:Knowledge:Lint 9: 6: 4: 3: 2: 1224: 1213: 1210: 1208: 1205: 1204: 1202: 1191: 1188: 1187: 1186: 1183: 1180: 1176: 1173: 1171: 1168: 1165: 1162: 1161: 1152: 1147: 1143: 1140: 1137: 1134: 1131: 1129: 1126: 1125: 1114: 1112: 1107: 1104: 1098: 1094: 1081:<font: --> 1074: 1070: 1066: 1056: 1052: 1043:. Then click 1037:Context title 1034: 1027:really means 1022: 1017: 1013: 1011: 1007: 1003: 989: 987: 983: 979: 975: 971: 969: 966: 964: 960: 956: 954: 950: 946: 942: 938: 934: 930: 926: 922: 918: 914: 910: 906: 902: 898: 894: 890: 886: 884: 881: 879: 875: 871: 869: 865: 861: 859: 856: 854: 850: 846: 844: 840: 836: 834: 833:User:Qwerfjkl 831: 829: 825: 821: 819: 815: 811: 807: 803: 799: 795: 791: 787: 783: 779: 775: 773: 770: 768: 764: 760: 758: 755: 753: 750: 748: 744: 730: 725: 713: 711: 708: 705: 704: 701: 699: 696: 694:26 March 2023 693: 692: 689: 687: 684: 681: 680: 677: 675: 672: 669: 668: 665: 663: 660: 657: 656: 653: 651: 648: 645: 644: 641: 639: 636: 633: 632: 629: 627: 624: 621: 620: 617: 615: 612: 610:25 March 2022 609: 608: 605: 603: 600: 597: 596: 593: 591: 588: 585: 584: 581: 579: 576: 573: 572: 561: 546: 543: 542: 533: 530: 526: 523: 520: 517: 514: 510: 509: 500: 496: 492: 488: 484: 480: 473: 469: 465: 462: 458: 453: 450: 446: 442: 435: 431: 427: 426: 424: 420: 417: 401: 391: 386: 385:accessibility 379: 378: 364: 363: 361: 358: 355: 354: 352: 348: 344: 340: 336: 333: 330: 327:Every page's 326: 322: 319: 316: 315: 314: 312: 308: 295: 292: 291: 288:Tracking only 283: 280: 278: 277:Stripped tags 275: 273: 270: 268: 265: 263: 260: 259: 251: 248: 246: 243: 241: 238: 236: 233: 231: 228: 227: 219: 216: 214: 211: 209: 206: 204: 201: 199: 196: 194: 191: 189: 186: 184: 181: 179: 176: 174: 171: 170: 167:High priority 164: 163: 153: 151: 147: 141: 137: 134: 124: 122: 118: 113: 109: 108: 101: 96: 83: 79: 78: 75: 70: 65: 61: 57: 54:, nor one of 53: 50:It is not an 47: 45: 39: 32: 31: 19: 1122:Other errors 1108: 1105: 1062: 1053: 1018: 1014: 1000: 752:User:Legoktm 747:User:Legobot 723: 682:5 March 2023 598:1 March 2022 586:17 June 2021 499:null editing 430:notification 423:Show preview 406:<div: --> 394:<div: --> 304: 294:Large tables 256:Low priority 159: 130: 105: 104: 41: 1077:<tt: --> 1025:{{/Header}} 622:1 July 2022 311:lint errors 42:This is an 1201:Categories 1158:Help pages 1151:MOS:SINGLE 1010:JavaScript 968:User:NicoV 625:11,116,651 613:13,845,831 601:15,349,584 589:22,450,097 577:24,083,947 347:talk pages 339:OK to edit 307:WikiGnomes 127:Background 1069:WikiGnome 1008:coded in 957:Inactive 847:Inactive 761:Inactive 735:Operator 709:3,496,968 697:3,996,924 685:4,999,462 673:5,998,634 661:6,984,595 649:7,994,445 637:8,890,312 449:See below 443:See also 345:and User 138:yesterday 60:consensus 1117:See also 1065:user CSS 1049:lintHint 491:lintHint 74:Shortcut 1101:@import 990:Active 872:Active 757:Task 41 569:Source 528:report. 506:Reports 459:-based 324:months. 82:WP:LINT 64:vetting 1087:, and 1006:gadget 972:Tasks 887:Tasks 862:Tasks 837:Tasks 776:Tasks 738:Tasks 493:, and 400:nowiki 337:It is 133:linter 1179:HTML5 1141:(816) 563:Date 457:regex 434:minor 402:: --> 160:From 142:today 110:is a 1111:here 1109:See 866:and 732:Bot 720:Bots 470:and 398:< 343:User 146:HTML 100:lint 62:and 1095:or 1203:: 1153:.) 1083:, 1079:, 1045:OK 1023:, 986:22 984:, 982:17 980:, 978:10 976:, 953:22 951:, 949:21 947:, 945:20 943:, 941:19 939:, 937:18 935:, 933:17 931:, 929:16 927:, 925:15 923:, 921:14 919:, 917:13 915:, 913:10 911:, 907:, 903:, 899:, 895:, 891:, 843:29 841:, 839:27 818:12 816:, 814:11 812:, 810:10 808:, 804:, 800:, 796:, 792:, 788:, 784:, 780:, 489:, 476:|} 152:. 131:A 974:7 909:9 905:8 901:7 897:4 893:2 889:1 868:2 864:1 806:9 802:8 798:7 794:6 790:5 786:3 782:2 778:1 451:. 66:. 46:. 20:)

Index

Knowledge:Lint
information page
encyclopedic article
Knowledge's policies or guidelines
consensus
vetting
Shortcut
WP:LINT
Illustration of linter gathering up various MediaWiki code markup
lint
The Linter extension
MediaWiki extension
Special:LintErrors
The MediaWiki wiki help page
linter
HTML
mw:Help:Extension:Linter § Why and what to fix
Special:LintErrors
Table tag that should be deleted
Misnested tag with different rendering in HTML5 and HTML4
Miscellaneous issues
Multiline table in list
Multiple unclosed formatting tags
Paragraph wrapping bug workaround
Self-closed tags
Old behaviour of link-wrapping font tags
Whitespace parsing bug
Unclosed quote in heading
Bogus file options
Fostered content

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.