On 1/14/15 8:28 AM, Anne van Kesteren wrote:
On Wed, Jan 14, 2015 at 2:00 PM, Boris Zbarsky <bzbar...@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
I think we're having a miscommunication here.
appearance:button can give you something that looks like a button. But
it doesn't _act_ like one.
What I'm asking is what people who want an actual button but with some
additional APIs on it are supposed to do. This is the basic idea of
subclassing built-ins: get something that acts like the built-in as far
as the browser is concerned but has some additional functionality on it.
-Boris
