This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27795 - clarify definition of "field" where relevant to scheme
Summary: clarify definition of "field" where relevant to scheme
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: CR HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-11 00:55 UTC by Nick Levinson
Modified: 2016-04-28 16:06 UTC (History)
2 users (show)

See Also:


Attachments

Description Nick Levinson 2015-01-11 00:55:41 UTC
In this one context, the word "field" is confusing: "Use only one scheme per field, or make the scheme declaration part of the value." (This appears under "scheme on meta elements" in section 11.2 (http://www.w3.org/TR/html5/single-page.html#non-conforming-features) and reference may also be made to the spec for HTML 4.01, sec. 7.4.4.2 (http://www.w3.org/TR/html4/struct/global.html#h-7.4.4.2).) Searching the single-page file for the string "field" yields over 100 matches, according to my browser, which includes mentions of form fields and "fieldset". In this context, is "property", "property-value pair", or something else meant? Please clarify this instance of "field".
Comment 1 LĂ©onie Watson 2016-04-28 16:06:06 UTC
Moved to HTML on Github:
https://github.com/w3c/html/issues/299