Myk Melez wrote: > When handling mouse click events, would it be possible for > BuildDisplayList to determine what the user clicked on based partly on > the opacity of the elements in the stack? > > Some websites have begun disabling user clicks on certain objects (i.e. > images) by overlaying them with a transparent element that captures the > event. > > I understand what websites are trying to do, but this seems like a bad > user experience for which the browser is partly responsible, since the > browser is in charge of making sure that a user's clicks have the effect > the user intends. > > We expose a preference for preventing web sites from disabling context > menus (ignoring calls to preventDefault in those cases). The overlay > technique is another way of disabling those menus. Shouldn't we allow > users to prevent it, too? > > For example, we might pass click events to the top-most object that is > at least n% opaque, where n is some number we determine through testing, > so elements have to be visible enough that users know what they're > clicking on.
I don't think we should start such an arms race. For one thing, it may be that the web site is using the transparent overlay to actually implement the effect the user intends (such as dragging a map). For another thing, sites would move to using transparent overlay images which would be harder to deal with, we'd end up having to test the opaity of individual image pixels. It would make the specification of what we actually do very very complex for Web authors. Rob _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
