- From: Lachlan Hunt <lachlan.hunt@iinet.net.au>
- Date: Thu, 19 Aug 2004 03:09:21 +1000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: lachlan.hunt@lachy.id.au, W3C CSS List <www-style@w3.org>
Boris Zbarsky wrote: > Quoting Lachlan Hunt <lachlan.hunt@iinet.net.au>: > >>I think it would be reasonable to expect that >>:active would also apply since something will, presumably, actually >>happen when it is activated. But, when there's no event handler > > See http://bugzilla.mozilla.org/show_bug.cgi?id=243459#c8 Yes, I'd already read that. > In short, the event handler that triggers may be attached to any ancestor, and > determining whether it "does something" is just the halting problen. I don't fully understand how it's a halting problem, though I'm not one who's implementing it, so maybe it is. Why can't it just detect if an event handler is attached to it during the capture, or bubble phase? It wouldn't matter if, technically, the attached function essentially does nothing, only that there is a handler attached to the element. Or have I completely misunderstood everything here? -- Lachlan Hunt http://www.lachy.id.au/ lachlan.hunt@lachy.id.au
Received on Wednesday, 18 August 2004 17:09:36 UTC