This shows you the differences between two versions of the page.
Previous revision | |||
— | spec:css3-regions:user-event-handling [2014/12/09 15:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Summary of this thread: | ||
+ | http:// | ||
+ | |||
+ | === Problem === | ||
+ | |||
+ | CSS regions act only as a visual containers for rendering content. Regions do not act as ' | ||
+ | |||
+ | This problem is not necessarily limited to regions. If other fragment containers can be an event target or have user action pseudo-classes, | ||
+ | |||
+ | === Proposals === | ||
+ | |||
+ | The email thread runs through several proposals along with a list of design considerations to evaluate the pros and cons of each. Of the proposals considered so far, these two have the most interesting characteristics: | ||
+ | |||
+ | 1. Add a new ' | ||
+ | |||
+ | Since the boxes for the fragmented nodes are displayed in the region box, the event would propagate from the fragment to the region, and on through the region' | ||
+ | |||
+ | 2. Change event propagation for fragmented content to hop to the fragment container at the fragment context boundary. | ||
+ | |||
+ | In the case of regions and named flows, events would propagate normally within the named flow content. But once they hit the named flow boundary, the event propagation would hop to the region where the user event originated, then up through the region' |