This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.w3.org/TR/microdata/ Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top Comment: Problem: providing that an input element of type checkbox has an itemprop, it's itemValue does not reflect the checked state of the element. The same could be said of other input elements or form elements. The common sense notion of an element's value isn't adequately represented in this working draft (20110113). I would like to see a more exhaustive definition in the Values section under Encoding microdata. I would also like to see text/mircodata+json become an alternative form encoding. The main advantage over application/x-www-form-urlencoded would be that the values are typed. http://www.google.com/recaptcha/mailhide/d?k=013K_1g0In4X12vDfRElYnaw==&c=CvQ9 SvC3Ni07o0ZgWt6IbdDlzuCVsd3RFMKsfp2-t2g= Posted from: 115.187.244.255
Section: http://www.w3.org/TR/2011/WD-microdata-20110113/#concept-property-value
(In reply to comment #0) > Specification: http://www.w3.org/TR/microdata/ > Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top > > Comment: > Problem: providing that an input element of type checkbox has an itemprop, > it's itemValue does not reflect the checked state of the element. The same > could be said of other input elements or form elements. The common sense > notion of an element's value isn't adequately represented in this working > draft (20110113). > > I would like to see a more exhaustive definition in the Values section under > Encoding microdata. What's the use case? > I would also like It'd be good if you could file separate bugs for separate issues.
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 2.
mass-move component to LC1