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 23825 - " hit testing" is not defined
Summary: " hit testing" is not defined
Status: NEW
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM View (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 07:46 UTC by David Burns :automatedtester
Modified: 2016-05-13 06:19 UTC (History)
3 users (show)

See Also:


Attachments

Description David Burns :automatedtester 2013-11-14 07:46:59 UTC
http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface

[[
 hit testing
]]

is not defined in the spec. There is a note slightly lower in the spec but it would be useful, at least for the WebDriver spec, would rely on this part of CSSOM especially "hit testing"
Comment 1 David Burns :automatedtester 2013-11-20 00:03:02 UTC
Pointer Events also seem to require a definition to hit testing for their specification. Put pointer in their meeting to this bug so am updating here too.

http://www.w3.org/2013/11/19-pointerevents-minutes.html#item03
Comment 2 Chris Rebert 2015-10-09 19:34:20 UTC
CSS UI 3 similarly depends on this but leaves it undefined:
https://github.com/w3c/csswg-drafts/commit/8eb712420eeb8144a96ff4092d62796184640cd3
Comment 3 Jordan Milne 2016-05-13 06:19:55 UTC
We should add a caveat that the hit testing function should not descend into subdocuments. 

The naive solution is to use the same hit testing function used for detecting which element should receive a click, but descending into cross-origin frames will leak information about the frame's contents via timing information. At least Firefox[0] and IE11 were affected by this.

[0]: https://bugzilla.mozilla.org/show_bug.cgi?id=950427