W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

[Bug 21522] New: Restore hasAttributes()

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Apr 2013 14:45:45 +0000
To: www-dom@w3.org
Message-ID: <bug-21522-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21522

            Bug ID: 21522
           Summary: Restore hasAttributes()
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
          Assignee: annevk@annevk.nl
          Reporter: ayg@aryeh.name
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

Either on Node or on Element -- probably on Element for consistency, since
.attributes is there (although I don't get why .attributes was moved from
Node).

Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=849661
WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=113580

Do we have any data suggesting pages don't use this?  There was one occurrence
in Gecko's codebase, and also in
<https://developer.mozilla.org/en-US/docs/JXON>.

I don't see the value in getting rid of it.  Testing "el.attributes" does the
same thing, but only if you actually have an Element, which is a dicey
assumption in JavaScript -- "el.hasAttributes()" will throw if you don't really
have an Element, which some authors might well prefer.

Are there any objections to restoring this to the spec?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 2 April 2013 14:45:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC