Last modified: 2014-02-12 23:35:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42607, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40607 - Add tracking category for pages that contain errors flagged by HTMLTidy
Add tracking category for pages that contain errors flagged by HTMLTidy
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-28 22:30 UTC by MZMcBride
Modified: 2014-02-12 23:35 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2012-09-28 22:30:55 UTC
The parser is aware if HTMLTidy found errors or not. If HTMLTidy finds (and auto-corrects) errors, these pages should be auto-categorized. Presumably the HTML can be fixed by humans or bots or something.

I guess there could be gradations, depending on how specific HTMLTidy is. That is, Category:HTMLTidy found very serious errors; Category:HTMLTidy found mildly serious errors; etc.
Comment 1 Nemo 2013-03-10 11:32:52 UTC
If bots can fix them, why aren't they also able to find them?
And if tidy auto-corrects them, why should humans bother "fixing" them?
Comment 2 MZMcBride 2013-03-10 11:35:13 UTC
(In reply to comment #1)
> If bots can fix them, why aren't they also able to find them?

HTMLTidy is being run server-side. It's vastly more convenient for the server to auto-categorize the pages. Then a bot will be able to easily find them. :-)

> And if tidy auto-corrects them, why should humans bother "fixing" them?

Graceful deprecation.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links