- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Feb 2011 23:05:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11347
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-07 23:05:45 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: Rejected
Change Description: no spec change
Rationale: Comment 1 still applies (and it answers many of the points made
after it). The exact user interface here is up to the browser vendors. They're
allowed to wait for the page to be loaded (though that's no guarantee that the
form is ready any more than not waiting at all, or waiting for </form>, or
waiting 10 minutes). My recommendation is to use the hidden="" attribute to
hide user interface elements that are not yet fully functional.
--
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 Monday, 7 February 2011 23:05:47 UTC