canmove, Confirmed users
2,675
edits
m (→Open Questions) |
|||
(6 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
* Allow a setting for enabling styles. | * Allow a setting for enabling styles. | ||
* Allow a setting for enabling comments. See {{bug|572642}} | * Allow a setting for enabling comments. See {{bug|572642}} | ||
* Have three element white lists: HTML, SVG and MathML. | ** Or always enable comments? (What about "--" in comments?) | ||
* <s>Have three element white lists: HTML, SVG and MathML.</s> | |||
** This turns out to lead to a lot of complexity without clear benefit. | |||
* Have three attribute white lists: HTML, SVG and MathML. The attributes don't depend on the element they are on beyond the element namespace. | * Have three attribute white lists: HTML, SVG and MathML. The attributes don't depend on the element they are on beyond the element namespace. | ||
** XXX: Figure out what the requirements are for attributes starting with data- or _. | |||
* Have three lists of attributes that take URLs. Drop the attributes when they have prohibited URLs (after trimming whitespace from the value). | * Have three lists of attributes that take URLs. Drop the attributes when they have prohibited URLs (after trimming whitespace from the value). | ||
** Resolve relative URLs into absolute ones using a per fragment base URL. (Is this correct for Gecko reqs? Current code uses the node's base URI. Is that right?) | ** Resolve relative URLs into absolute ones using a per fragment base URL. (Is this correct for Gecko reqs? Current code uses the node's base URI. Is that right?) | ||
** However, allow any URL in the src attribute on the img element, because imgs are safe. {{bug|572637}} | ** However, allow any URL in the src attribute on the img element, because imgs are safe. {{bug|572637}} | ||
* Have a list of SVG attributes that take different-document references. | * Have a list of SVG attributes that take different-document references. | ||
Line 21: | Line 23: | ||
* Can stylistic SVG attributes have values that need to be sanitized? | * Can stylistic SVG attributes have values that need to be sanitized? | ||
* Should Semantic MathML be on the white list for clipboard round-tripping? (Mainly a footprint issue.) | * Should Semantic MathML be on the white list for clipboard round-tripping? (Mainly a footprint issue.) | ||
* Is it dangerous for SVG fragment id references to be able to refer to an id in the document the untrusted fragment gets inserted into? | |||
* What to do about microdata? | |||
==Non-Gecko Requirements== | ==Non-Gecko Requirements== | ||
These are features for the HTML5 parser when it is used outside Gecko. | |||
* Allow form-related elements to be toggled on and off in the white list. | * Allow form-related elements to be toggled on and off in the white list. | ||
* Allow using the sanitizer in non-fragment mode (in which case, the title element should be allowed). | * Allow using the sanitizer in non-fragment mode (in which case, the title element should be allowed). | ||
** Are there compelling use cases for non-fragment mode sanitization? | ** Are there compelling use cases for non-fragment mode sanitization? | ||
* Have a configurable white list of URL schemes. | * Have a configurable white list of permitted URL schemes in attributes that take URLs. |