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 8742 - User informed when URI can#t be resolved
Summary: User informed when URI can#t be resolved
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/TR/html5/history.ht...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-01-14 11:34 UTC by Gez Lemon
Modified: 2010-10-04 14:56 UTC (History)
4 users (show)

See Also:

Attachments

Description Gez Lemon 2010-01-14 11:34:39 UTC 
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.
Comment 1 Michael Cooper 2010-02-11 17:26:47 UTC 
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.
Comment 2 Ian 'Hixie' Hickson 2010-02-17 22:22:43 UTC 
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.