- From: <bugzilla@jessica.w3.org>
- Date: Thu, 07 Feb 2013 18:19:08 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17174 Edward O'Connor <eoconnor@apple.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |eoconnor@apple.com Resolution|--- |WONTFIX Assignee|dave.null@w3.org |eoconnor@apple.com --- Comment #4 from Edward O'Connor <eoconnor@apple.com> --- 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: This has been proposed many times in the past, and has been rejected for several reasons. The "HTML should support href on any element" entry of the WHATWG FAQ captures several of the known issues with such a feature: http://wiki.whatwg.org/wiki/FAQ#HTML_should_support_href_on_any_element.21 Some additional history on this issue from as far back as 2006 that I could find: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-January/005407.html http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-August/007179.html http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-July/015482.html This has also come up on public-html several times, though I found it more difficult to locate specific threads. Though about src="" and not href="", you may find this thread illuminating: http://lists.w3.org/Archives/Public/public-html/2007JanMar/0678.html -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 7 February 2013 18:19:10 UTC