Re: Fwd: Pointer Events spec

Missed description for test case:

To test implicit 'pointer capture' start pointer at border of one of blocks
(e.g. one with green border) and move then faster to the another block and
then release pointer. Now console.log should show situation.


2014-04-16 17:54 GMT+04:00 Arthur Stolyar <nekr.fabula@gmail.com>:

> Made test case here: http://jsbin.com/yayagoyi/1
> Code on which I tested is not changed there, even comments.
>
>
> 2014-04-16 17:45 GMT+04:00 Patrick H. Lauke <redux@splintered.co.uk>:
>
> On 16/04/2014 14:15, Arthur Stolyar wrote:
>>
>>> Tested on Windows Emulator 12.0 (Window 8.1) with touch events
>>> emulation. It seams that IE has implicit 'pointer capture' for element
>>> which may trigger scroll. i.e. if element has 'touch-action: pan-x
>>> pan-y' or just 'touch-action: auto' CSS property, when all events
>>> between pointerdown and pointercancel 'll be fired on that element. It
>>> means that if pointer leaves boudaries of that element, then pointerout
>>> and pointerleave 'll be fired, but not pointerover and pointerevent on
>>> new target. Also, IE has some strange behavior with 'pointer capture',
>>> when IE fires pointerout on element with 'pointer capture' then
>>> relatedTarget property of event 'll be null, but when IE triggers
>>> pointerleave on element with 'pointer capture' then relatedTarget
>>> property of that element 'll be same element as in target property of
>>> event.
>>>
>>
>> Do you have a test case/demo? Happy to test on an actual Win8.1
>> touchscreen laptop, as it may well be that what you're seeing is an
>> artifact of running it in emulator.
>>
>> P
>> --
>> Patrick H. Lauke
>>
>> www.splintered.co.uk | https://github.com/patrickhlauke
>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>
>>
>
>
> --
> @nekrtemplar <https://twitter.com/nekrtemplar>
>



-- 
@nekrtemplar <https://twitter.com/nekrtemplar>