W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10331] Clarify meaning of "defined to contain a URL" and "defined to contain one or more URLs"

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Sep 2010 23:31:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P0jeQ-0002d9-KU@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10331

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-28 23:31:57 UTC ---
usemap isn't defined to take a URL, it's defined to take valid hash-name
reference. That seems quite clear.

form.action is a URL (this is intentionally not like non-IE browsers, since
IE's behaviour makes more sense).

The legacy ones are all plain text (not URLs), since none are defined to be
URLs. This is explicitly stated for body.background for some reason, but it's
true for all the others as well.

I would really rather not go through marking all the URL-reflecting IDL
attributes explicitly, since that's just a huge pain and I'm bound to make
mistakes, both in doing it and later in maintaining it.

I'd accept a patch against the "source" file, though, if you feel strongly
about this and want to do it. Feel free to contact me on IRC if you need help
with that.


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: Spec seems well-defined as is.

-- 
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 Tuesday, 28 September 2010 23:32:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC