Closed btylerburton closed 1 week ago
URLs have been sanitized, but string literals still need to be escaped...
<meta property="og:description" content="{{ h.literal.escape(notes) }}">
produces:
<meta property="og:description" content="The "Watershed Boundary Dataset (WBD)" from The National Map (TNM) defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The...">
CKAN defines a string escape helper below but it seems to have no effect.
User Story
In order to ensure a dataset's markup is valid, datagovteam wants to escape the content put into the tags.
Results of HTML validator scan should report no errors: https://validator.w3.org/nu/?doc=https%3A%2F%2Fcatalog.data.gov%2Fdataset%2Fdob-now-build-elevator-permit-applications
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
Background
Bad html markup is causing issues with google search console.
Example: https://catalog.data.gov/dataset/dob-now-build-elevator-permit-applications
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch