9928 2010-06-15 11:03:39 +0000 The "dirty value" concept should be removed or used more 2010-10-04 14:45:34 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED FIXED P2 enhancement --- 1 mounir ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36177 0 mounir 2010-06-15 11:03:39 +0000 The specs say: "Each input element has a boolean dirty value flag. When it is true, the element is said to have a dirty value. The dirty value flag must be initially set to false when the element is created, and must be set to true whenever the user interacts with the control in a way that changes the value." However, the "dirty value" concept is used only once (a few lines below). The "dirty value flag" is always used instead. To make things more clear, the "dirty value" concept could be removed or should be used more often ? 38039 1 ian 2010-08-27 21:02:28 +0000 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 38040 2 contributor 2010-08-27 21:10:15 +0000 Checked in as WHATWG revision r5375. Check-in comment: simplification http://html5.org/tools/web-apps-tracker?from=5374&to=5375