Open LaurensBurger opened 2 months ago
Needs stakeholder to pick this up - I've had a post-it on my desk for months now with the solution (removing the WYSYWIG layer from the admin) and disallowing HTML tags. The latter bit may not be accepted by all stakeholders, so we need some discussion about the way forward.
Refinement: Can we see in the code/related issue who requested HTML-tags? In my opinion we should just remove the WYSIWYG editor. If I remember correctly, this was about a way to make the privacy-link-text editable. Maybe we can ONLY allow the "a"-element and not make it fully WYSIWYG .
This was estimated on: Assumption that its just a WYSIWYG editor for this label. Maybe something like this: {% link "privacy page" %}
while the actual link is configured in the admin. Final direction to be decided, but 1 day?
Product versie / Product version
2.6.x - latest
Customer reference
No response
Omschrijf het probleem / Describe the bug
As mentioned in #3415
This is still an issue:
Stappen om te reproduceren / Steps to reproduce
No response
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response