Closed
Bug 1170199
Opened 9 years ago
Closed 9 years ago
[Compat Data][Importer] Detect pages without compatibility data
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwhitlock, Assigned: jwhitlock)
References
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature])
What problem would this feature solve? ====================================== The feature mirror tool adds all pages under an MDN path prefix, such as Web/*. This includes pages without compatibility data, such as the Web/API index [1] and XSLT technology [2]. These are usually reported as doc parse errors. [1] https://browsercompat.herokuapp.com/importer/1358 [2] https://browsercompat.herokuapp.com/importer/5704 Who has this problem? ===================== Core contributors to MDN How do you know that the users identified above have this problem? ================================================================== Reported in DevEngage meeting June 1st How are the users identified above solving this problem now? ============================================================ Ignoring pages in problem topics or known to not have compat data. Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== Skip parsing a page and mark it "No Data" if it doesn't include: - A section titled "Specifications" - A section titles "Browser Compatibility - The {{CompatibilityTable}} macro Is there anything else we should know? ====================================== If a false negative is found (a page without these elements but with compat or specification data), a bug can be filed to improve the "no data" detection.
Assignee | ||
Comment 1•9 years ago
|
||
I've updated https://browsercompat.herokuapp.com/importer/ and submitted the code in PR #35: https://github.com/jwhitlock/web-platform-compat/pull/35 There is a drop in reported issues, from 7091 to 6103. See the pull requests for detailed counts.
Assignee | ||
Comment 2•9 years ago
|
||
Oops, PR was against wrong repo. Fixed: https://github.com/mozilla/web-platform-compat/pull/37
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jwhitlock
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 3•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/45d962cf73c34e3d5326509379ed0396153e8cee fix bug 1170199 - Detect pages w/ no data If a page doesn't include strings identifying a Browser compatibility section, a Specifications section, or the CompatibilityTable KumaScript macro, then stop parsing. Detection is done with strings, not regex, so it should be fast but maybe with false positives.
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•