Re: handling click events on :before/:after pseudo-elements

On Tue, Nov 6, 2012 at 11:31 AM, David Karger <karger@mit.edu> wrote:
> I've run into an under-specification in css that has apparently led firefox
> and chrome to choose different behaviors; either is fine, but it would be
> nice if the css specification were extended to encourage consistency.
>
> The question is: if I declare some content to be inserted via the :before or
> :after pseudo elements, how should the event model handle clicks *on* the
> inserted content?  In firefox, clicking on the pseudo-content triggers a
> click event on the element that has been styled with the pseudo content; in
> chrome, it does not (the click falls through to whatever element is "behind"
> the pseudo content).
>

Do you have an example of when this happens in WebKit? It's a bug, and
I think it's fixed with my rewrite of how we handle generated content.

- E