8742 2010-01-14 11:34:39 +0000 User informed when URI can#t be resolved 2010-10-04 14:56:17 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED NEEDSINFO http://www.w3.org/TR/html5/history.html#following-hyperlinks a11y P2 normal --- 1 gez.lemon ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31033 0 gez.lemon 2010-01-14 11:34:39 +0000 The specification states: "If resolving the URL fails, the user agent may report the error to the user in a user-agent-specific manner, may navigate to an error page to report the error, or may ignore the error and do nothing." The final option is to ignore the error and do nothing. The user should get an error message that is accessible and understandable. 31836 1 cooper 2010-02-11 17:26:47 +0000 Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future. 32298 2 ian 2010-02-17 22:22:43 +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: Did Not Understand Request Change Description: no spec change Rationale: The browser is allowed to give "an error message that is accessible and understandable", that's the penultimate option. Are you saying the browser should _not_ be allowed to ignore the error and do nothing? If so, that seems like an issue for the user agent, not an issue for the spec. Note that there are many cases where the user doesn't even know a navigation is taking place, so telling the user about every error would be a very poor user experience. Could you elaborate on what exactly you are concerned about? Maybe a concrete example of the problem would be helpful in aiding my understanding.