Closed
Bug 1140009
Opened 9 years ago
Closed 9 years ago
[Compat Data][Importer] Extra cell should be error, not break parser
Categories
(developer.mozilla.org Graveyard :: General, defect)
developer.mozilla.org Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwhitlock, Unassigned)
References
Details
(Whiteboard: [specification][type:feature])
What problems would this solve? =============================== When a compatibility table has a row with an extra cell, the parser raises a ValueError trying to find the matching column header. Instead, this should be marked as an error that needs to be fixed by a human. Who would use this? =================== MDN staff cleaning data for the import process What would users see? ===================== Users would see the extra cell with surrounding context What would users do? What would happen as a result? =================================================== Users would remove the correct extra cell. Is there anything else we should know? ====================================== https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet is an example of a page w/ error, https://browsercompat.herokuapp.com/importer/1019 with the parse failure.
Reporter | ||
Updated•9 years ago
|
Comment 1•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/1404095df1e3449f22ecd97b17beadbff306f95c fix bug 1140009 - Detect extra compat cells Was an error that halted parsing. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet, in the mobile table.
Updated•9 years ago
|
Status: UNCONFIRMED → 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
•