- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Apr 2013 06:28:04 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21749
Bug ID: 21749
Summary: Setting a capture on an offshore element
Classification: Unclassified
Product: PointerEventsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Pointer Events specification
Assignee: jrossi@microsoft.com
Reporter: jrossi@microsoft.com
QA Contact: public-pointer-events-bugzilla@w3.org
CC: public-pointer-events@w3.org
>From Francois Remy:
http://lists.w3.org/Archives/Public/public-pointer-events/2013AprJun/0084.html
Here’s a test case for your consideration where, I believe, IE10 is distant
from the official specification:
<!doctype html>
<html onmspointerdown="eatPointer(event.pointerId)"
onmspointermove="if(event.button>=0)
console.log(event.clientX+','+event.clientY)">
<head>
<title>Some pointer events test</title>
<script>
var x = document.createElement("div");
function eatPointer(id) {
x.msSetPointerCapture(id); // will throw
}
</script>
</head>
<body>
</body>
</html>
I believe the spec does not say the capture should fail, and therefore it
should not. That would mean, however, that the capture may end up happening on
a different window than the one the event was fired for, something which can be
a problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 19 April 2013 06:35:43 UTC