This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.10.7 says "Some states of the type attribute define a value sanitization algorithm." While it's true that some of the types define algorithms, we could not find a place where the goal of "value santiation" was defined. The term "value santitation algorithm" appears as a link within this section, and links back to the top of the section.
mass-move component to LC1
What do you mean by goal? If you mean rationale, that is missing for many features. See http://wiki.whatwg.org/wiki/Rationale for an attempt at addressing this gap.
I mean something that answers the question "what is a value sanitation algorithm" or "what is value sanitation?" in general. All I could find was examples of specific value santiation algorithms. What do they have in common that makes them the same kind of thing? What are they sanitizing, and what was unclean about it?
It's just a term on how to process controls.
Cynthia, I notice you assigned this to Anne. Was that intentional?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 5
Trying again... What I'm looking for is a glossary defintion of "value sanitation" or "value santitation algorithm." Here's what I can gleen from the spec. Is this close? Value Santiation Algorithm: An algorithm to convert the value of an input element's @value attribute to the appropriate data type for that input. For example, to convert a string to a number or a date object.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It's just an opaque term. It could be called "bunny rabbits algorithm" and the spec would have the same normative meaning. It's just a phrase used so that one part of the spec can invoke text given elsewhere in the spec. I don't really understand what a definition would be.