W3C home > Mailing lists > Public > public-html-admin@w3.org > August 2013

[Bug 22914] New: Unclear if setting element.dataset.fooBar should update data-foo-bar attribute

From: <bugzilla@jessica.w3.org>
Date: Sun, 11 Aug 2013 13:55:25 +0000
To: public-html-admin@w3.org
Message-ID: <bug-22914-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22914

            Bug ID: 22914
           Summary: Unclear if setting element.dataset.fooBar should
                    update data-foo-bar attribute
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: karger@mit.edu
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

Spec section 3.2.3.9 on custom data attributes specifies how hyphenated data-*
attribute names are converted to camelCase for inclusion in an element's
dataset which is a DomStringMap.  And precise specifications are given for how
names are read and updated in a DomStringMap.  However the specification is
mute on whether an update to a name's value in the DomStringMap should cause an
update to the corresponding content attribute in the underlying element.  

In jquery, for example, data-* attributes are read into the DomStringMap on
first access, but changes to the corresponding values in the DomStringMap are
*not* pushed back as changes to the DOM node's content attributes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Sunday, 11 August 2013 13:55:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:24 UTC