25482 2014-04-27 09:57:55 +0000 restrict roles on form element? 2014-04-30 06:03:02 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX P2 normal --- 1 faulkner.steve eoconnor dominicc eoconnor faulkner.steve jcraig mike mzehe public-html-admin public-html-wg-issue-tracking schwer surkov.alexander public-html-bugzilla oldest_to_newest 104503 0 faulkner.steve 2014-04-27 09:57:55 +0000 seems unwise to allow any role on form element 104504 1 faulkner.steve 2014-04-27 10:01:13 +0000 currently for element can have any role assigned is this appropriate? 104631 2 eoconnor 2014-04-28 23:39:38 +0000 Why? Offhand, I think there are a bunch of ARIA roles that could sensibly apply to the form element. Just to name a couple: alertdialog, application. 104677 3 schwer 2014-04-29 13:02:08 +0000 I see no value in restricting it. We should not be restricting ARIA roles unless absolutely necessary as it then creates a situation where the author has to keep track of all the exceptions. Most authors don't go back to look at the spec. ARIA and the FORM element have been in place for years and we have never seen an issue with the fact that the ARIA role is unrestricted here. I recommend we close this. 104707 4 eoconnor 2014-04-29 20:07:11 +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: Rejected Change Description: No change. Rationale: I agree with Rich. [Never thought I'd say that :)] 104782 5 faulkner.steve 2014-04-30 06:03:02 +0000 (In reply to Edward O'Connor from comment #4) > 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 change. > Rationale: I agree with Rich. [Never thought I'd say that :)] I can live with this, I was asking a question in Comment 1 it got answered :-) Ted - FYI we don't need to add response boiler plate any more - new lighter weight process