Hacker News Reader

Comment by pestaa | Hacker News Reader

Neither. The problem is that your browser handles click events on an invisible layer.

Well, no; there's two problems now. The first one is that your browser will handle click events on invisible and near-invisible layers. The second one is that your browser will allow click events to flow through opaque and near-opaque layers.

Yes, there is a different term for each case, but both boils down to "if I can't see it, why would I click it".

I hope this doesn't mean the end of niche browsers, or at least not those built on well-known rendering engines like WebKit.

This is just another brick in the wall. The web is /not/ a platform that's friendly to new implementations, and it never will be; the complexity that's constantly being added ensures this. It also means we're all going to have a lot fewer guarantees of anything like sane behavior when using the web in the years to come.

Those are not bugs, IMO.

A lot of web Javascript would be useless if events didn't bubble, and being able to define invisible click areas is useful in a variety of contexts.

Sucks that a few people are going to be malicious about it but I think the benefits outweigh the drawbacks.

The problem is not that events bubble, but that clicks fall through visible layers to lower ones and get caught invisible ones on top of what you intended to click on.

Invisible click areas as you called it are not the same as multi-layered click targets imho.

Reply on news.ycombinator.com