[Bug 8742] User informed when URI can#t be resolved

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8742


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NEEDSINFO




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-17 22:22:43 ---
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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 17 February 2010 22:22:45 UTC