-
-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hook on element/attribute removal #881
Comments
Sounds great, this is a good idea - want to spin up a PR? Happy to review once done. |
@Deltaxel btw, before we start building anything, have you already looked at |
Also, please check the commit above, experimentally added hooks to removal methods. |
Hey, sorry for not replying sooner |
Ah, you are right. But, I still wonder - if it's just about telemetry, do we really need the hooks? |
I strongly believe that this can be done already and quite easily with the tools we already offer, closing the ticket, please reopen if any other use-cases arise |
You are right |
Cool, thanks :) If that doesn't work, we can look into the extra hooks ofc. |
Background & Context
We have a lot of customers adding content to our application. Some of the content being removed by DOM Purify should be kept.
We're not always aware of every tag/attribute our customers are using. So we would like to add some telemetry to keep track of removed content and act quickly when an issue is detected.
This could also help identify potential malicious users.
Input
Given output
No handler called withExpected output
Handler called withFeature
I would add a uponRemovedElement and a uponRemovedAttribute hooks.
The text was updated successfully, but these errors were encountered: