-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[4.0] Allow form elements in a subform template (sanitisation) #34514
Conversation
hm, do we really need cleaning for subform "template"? |
This is exactly what's not allowed and what the sanitizer is supposed to clean 😉 |
then subfrom will be broken for these fields, |
Hard call (thankfully not my call). Allowing inline on-events is XSS prone. Disallowing on-events is stricter but probably all elements will be required to be defined custom-elements (own constructor etc). I'm ok reverting this. @wilsonge your call... |
I understood the intention, and it good one. |
Till there's a viable solution for sanitization of the subform templates the changes have been reverted |
I have tested this item ✅ successfully on 934208e This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/34514. |
1 similar comment
I have tested this item ✅ successfully on 934208e This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/34514. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/34514. |
Thanks! |
Pull Request for Issue #34512 (the subform part) .
Summary of Changes
Testing Instructions
Actual result BEFORE applying this Pull Request
Expected result AFTER applying this Pull Request
Documentation Changes Required
@wilsonge can you push the button here?