Description
We show Z89/HTML fragments in raw code form to users on Wikifunctions.org. This is inimical to usage. Now that we have a sanitisation API, we should re-design how the component works on the front-end so that users can see the rich content, but there are use cases that also want the raw HTML, so we should provide for a mechanism to show that too / instead.
Desired behavior/Acceptance criteria
- As a user, I should be able to see the rich text form when Z89/HTML fragment components are available, on evaluator results, on test cases, and elsewhere.
- As a sysadmin, I should be confident that all rendered rich text fragments have been consistently sanitised to avoid XSS / etc. concerns.
- As a user, I should be able to inspect the raw HTML underlying the fragment, so e.g. I can check the output of a Test case is exactly correct.
Devices and Design (URLs or screenshots)
- Desktop: ...
- Small screens/mobile: ...
Completion checklist
- Functionality:
- The solution meets the expected behavior/acceptance criteria described above
- All the child tasks are closed
- The issue has been peer reviewed
- The issue has been merged
- Engineering:
- There are existing and passing unit/integration tests effectively testing its success and its failure
- All new classes/methods are covered by unit tests
- Design:
- Design review of live version in accordance to design standards
- Documentation:
- All new functions/methods are annotated
- Accessibility:
- New functionality is compared against the Accessibility guide for developers
- Accessibility concerns are either address or, if the work is sufficiently large, a new Phabricator ticket is created and linked to this ticket
- All user facing strings are internationalized
