W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Custom Elements: 'data-' attributes

From: Brian Kardell <bkardell@gmail.com>
Date: Thu, 15 May 2014 12:22:16 -0400
Message-ID: <CADC=+jd4byXMPEJgV3B-MTk-zhVHdQ77VzmdY1HUoMKgDsYpgA@mail.gmail.com>
To: Soledad Penadés <sole@mozilla.com>
Cc: "public-webapps@w3c.org" <public-webapps@w3c.org>
On Wed, May 14, 2014 at 7:18 AM, Soledad Penadés <sole@mozilla.com> wrote:


> And that's where I suggested leaving attribute handling to the component.
> If it "self-registers" as handling a certain attribute, then don't let the
> UA handle it as it would do if unregistered.
I'm not sure what this means by UA handling, can you explain?  Let me give
you a concrete example and you can tell me what happens.  I work in higher
education, and we have custom elements for things like student's schedules
- showing them, making them, etc.  And we have lists of courses, etc.  Lots
and lots of stuff that has to do with classes (the kind that are taught)
and these classes have unique ids and titles too.  So what happens when I

<x-item class="WEB101">


<x-item class="WEB200" title="Intermediate Webby Thingz">


<x-offering class="WEB500" id="21_asdfasdWEFMD" title="Using AppCache">

These are important things to our component, so, probably I would register
them - but both class and offering mean something as global attributes, and
these are plugged into all sorts of things - CSS, qsa, etc...   When you
say "then don't let the UA handle it as it would do if unregistered" - what
does that mean in this case?  anything?  Would that all still continue to

I'm just trying to understand what you are suggesting there...


> --
> //
> // http://soledadpenades.com   //  @supersole //
> // GIF HACKTIVIST // Mozilla Apps Engineering //
>                                               //

Brian Kardell :: @briankardell :: hitchjs.com
Received on Thursday, 15 May 2014 16:22:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC