collective / collective/experimental.safe_html_transform

Making tinyMCE use the safe_html filter configuration

Open
#19 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

As we know the safe_html does filtering on server side and tinyMCE works on client side and as the tinyMCE has its own filter criteria so there may be differences in the filtering for the text from safe_html and tinyMCE so we will try to configure tinyMCE according to safe_html so to match the filter criteria between them and also the filter criteria will match both at server and client.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue concerns matching tinyMCE's client-side filtering with the safe_html server-side filter, but it names no files, tests, or entry points. Start by locating the tinyMCE configuration and safe_html filter implementation; done means their allowed filtering criteria are aligned and the behavior is verified on both sides.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
frontend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.