- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 06 Jan 2010 05:39:34 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8459
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-01-06 05:39:34 ---
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 spec change
Rationale: Certainly there are environments where 500ms is excessively short
(satellite links aren't the half of it; consider mobile phone networks!). There
are also environments where it's too long (e.g. when I'm on a network backbone
link, there really is no reason to wait more than 100ms for anything that's
being served from the same coast). It is just an example, intended to
illustrate possible criteria that a user agent could use. User agents are
expected (as is implied by that paragraph) to pick whatever is best for their
users.
--
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, 6 January 2010 05:39:36 UTC