[Bug 15954] [Shadow]: The dilemma of document DOM tree mutations

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15954

FremyCompany <fremycompany_pub@yahoo.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fremycompany_pub@yahoo.fr

--- Comment #9 from FremyCompany <fremycompany_pub@yahoo.fr> ---
See some discussion on the same subject here:
http://www.w3.org/mid/7ECB8D8C436C41D4B08A35B21B7DBB44@FREMYD2

I guess my proposal and Tab's one are fairly similar (just to avoid you the
pain of clicking, here's how it would look like):

    /* CSS CODE */
    @virtual-namespace tab-data "http://jquery.com/namespaces/tab-data";
    h2[tab-data|selected] {
        ...
    }

    /* JS CODE */
    var tabData = getVirtualNamespace("http://jquery.com/namespaces/tab-data");

    // add the virtual attribute to the element
    tabData.set(element, "selected", "true");

    // remove the virtual attribute
    tabData.set(element, "selected", null);

It's also possible to use a normal namespace and suppose that leaking prefixed
attributes is not an issue as they don't collide with natural attibutes. That
solution is already OK and don't need any change from browser makers.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.