Should we rename this, similarly to html5-h? Would "html5-disclosure" actually work, or would it appear to conflict with details/summary too much?
Or should we keep the repo name ("disclosure-button") and just apply that to the custom element's HTML and spec? That sounds good, too, as it is a disclosure button :-).
I've been thinking about this, and I would like to make the case for fully adopting "disclosure-button"...
"disclosure-button"
Pros
Anyone can instantly tell what it does.
Also the name indicates that it's just the button part, which is accurate (it affects an element that already exists on the page).
Cons
Fixes us at using a button; but this can be styled to not look like a button if need be (and, semantically, it feels like a button). We could make it easy to sub an image for the button later on, too.
"html5-disclosure"
Pros
It matches one of our other repo's names. I really can't think of any decent plus points.
Cons
It's not instantly clear what it does from the name. With this one, I don't think we're angling to get it in the spec per se (though it would be great if so many people used it that it were adopted), so naming it after the standard is not a priority. The priority is ease-of-use for web devs (so that it gets adopted), and "html5-disclosure" is not as easy-to-use as "disclosure-button".
Should we rename this, similarly to html5-h? Would "html5-disclosure" actually work, or would it appear to conflict with details/summary too much?
Or should we keep the repo name ("disclosure-button") and just apply that to the custom element's HTML and spec? That sounds good, too, as it is a disclosure button :-).