Closed Bug 1093120 Opened 11 years ago Closed 11 years ago

[Compat Data] Improve handling of HTML in feature names

Categories

(developer.mozilla.org Graveyard :: General, defect)

All
Other
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Whiteboard: [specification][type:bug])

What did you do? ================ 1. Find feature ID of a feature with HTML in the name, such as (http://doesitwork-dev.allizom.org/api/v1/features?slug=web-css-resize-basic_support_on_textarea_) 2. Load that feature in the browse app (http://doesitwork-dev.allizom.org/browse/features/2104) What happened? ============== The display of features with HTML in the name includes the rendering of that HTML What should have happened? ========================== The HTML should be escaped, i.e. "&lt;" for "<" Is there anything else we should know? ====================================== This will probably require fixes in the importer as well as the display logic.
Blocks: 996570
Severity: normal → minor
Works for me, isn't it already fixed?
Flags: needinfo?(john)
I've fixed the code and updated http://doesitwork-dev.allizom.org. The bug is waiting on a code review, which should be done in the next few days: https://github.com/mozilla/web-platform-compat/pull/14
Flags: needinfo?(john)
Commit pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/84a9e7589b412a9431516207b3c123153daba164 fix bug 1093120 - Handle HTML in feature names On import from the webcompat scraped data, feature names and notes are HTML escaped. In the browse app, MDN paths are escaped on display.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.