- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 14 Jan 2015 14:28:50 +0100
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Domenic Denicola <d@domenic.me>, "public-webapps@w3.org" <public-webapps@w3.org>
On Wed, Jan 14, 2015 at 2:00 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Wanting things like custom buttons is _very_ common. What is your proposal > for addressing this use case? I have no good answer. appearance:button seems to work okayish (prefix needed though). However, this also seems like a different problem than letting developers create an element from scratch and exposing the necessary lifecycle hooks to enable that. Furthermore, if the solution is this much of a hack, perhaps addressing a smaller problem first (just custom elements, not subclassing normal elements) is a good idea. And then once that has matured somewhat we can revisit. There's no need to do both at once, I think. -- https://annevankesteren.nl/
Received on Wednesday, 14 January 2015 13:29:15 UTC