Support standard attributes in TABLES Policy - #326
Conversation
|
I am sorry, @mikesamuel is the release master. He'll get on this as soon as he can. Forgive the delay! |
|
Hello. What is the current thinking on this? Is "colspan","rowspan" generally safe to allow? |
9bb458a to
f40152f
Compare
|
PR #378 has just been merged and adds |
|
Closing as superseded. The colspan/rowspan half landed via #378, and this branch still patches the pre-#379 |
Salvages the two attributes from PR OWASP#326 that OWASP#378 did not already cover. - headers on td and th: a space-separated list of ID tokens limited to ASCII letters, digits and _ - . : with white-space collapsed. - scope on th: row, col, rowgroup or colgroup, matched case-insensitively and emitted in canonical lower case. OWASP#326's policy compared the lowercased value but returned the original. Positive and negative tests in SanitizersTest; changelog entry crediting the original author. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BZfawfTUAFHN7cocUjcpQK
Fixes #195 and allows more attributes than existing PR
The goal is to allow common safe attributes in table context for in a single PR instead of handling one attribute at a time. Pl let me know if we want to allow more, or if there are issues with this one.