11221 2010-11-04 15:42:08 +0000 Contradiction regarding isindex (the special form input field) 2016-07-06 20:05:48 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WORKSFORME whatwg-resolved P2 editorial --- 1 pantalaimon176 travil mike plh public-html-admin public-html-wg-issue-tracking travil zcorpan public-html-bugzilla oldest_to_newest 42131 0 pantalaimon176 2010-11-04 15:42:08 +0000 Where isindex is defined (http://www.w3.org/TR/html5/association-of-controls-and-forms.html#attr-fe-name-isindex) it states: > This value, if used as the name of a Text control that is the only control in a > form that is submitted using the application/x-www-form-urlencoded mechanism, > causes the submission to only include the value of this control, with no name. So an isindex can be the only control in the form. The urlencoded encoding algorithm (http://www.w3.org/TR/html5/association-of-controls-and-forms.html#application-x-www-form-urlencoded-encoding-algorithm) states on step 4.5: > If the entry's name is "isindex", its type is "text", and this is the first > entry in the form data set, then append the value to result and skip the rest of > the substeps for this entry, moving on to the next entry, if any, or the next > step in the overall algorithm otherwise. So an isindex doesn't have to be the only control - merely the first (in the tree). To me, the former makes more sense than the latter. It also reduces the risk of someone accidentally (eg) using a hidden form field named "isindex" in their form, then discovering that it doesn't show up in the submission as the expected isindex=value pair. 81712 1 robin 2013-01-21 15:59:15 +0000 Mass move to "HTML WG" 81830 2 robin 2013-01-21 16:02:02 +0000 Mass move to "HTML WG" 125877 3 travil 2016-04-15 21:44:10 +0000 HTML5.1 Bugzilla Bug Triage: The isindex element as a formal element has been removed (sometime in the past). This should resolve the contradiction. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks! 126892 4 zcorpan 2016-07-06 20:05:48 +0000 https://github.com/whatwg/html/pull/1095