This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21132 - Regions need a way to respond to events in their content fragment
Summary: Regions need a way to respond to events in their content fragment
Status: RESOLVED LATER
Alias: None
Product: CSS
Classification: Unclassified
Component: Regions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Alan Stearns
QA Contact: public-css-bugzilla
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
: 15679 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-26 23:02 UTC by Alan Stearns
Modified: 2013-06-24 22:34 UTC (History)
3 users (show)

See Also:

Attachments

Description Alan Stearns 2013-02-26 23:02:21 UTC 
http://lists.w3.org/Archives/Public/www-style/2012Nov/0173.html

If a content element receives a click, touch or drag event, the event bubbles up through the content element's place in the DOM, and the region that displays the content (and its parents) never hear about it.
Comment 1 Alan Stearns 2013-04-05 00:34:34 UTC 
*** Bug 15679 has been marked as a duplicate of this bug. ***
Comment 2 Alan Stearns 2013-06-24 22:34:41 UTC 
An elementsFromPoint() method has been added to CSSOM-view:

http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface

This will in most cases allow code to determine which fragment container has been clicked. It will not fix CSS hover styling.

An additional 'paint-order' value for pointer-events is proposed for a future level of CSS UI:

http://wiki.csswg.org/spec/css4-ui?&#pointer-events

This would optionally allow user events to pass through the stack of elements under the event coordinates. This would the issue for both click events and CSS hover styling in fragment containers.