Difference between revisions of "Template:Issues/SVC-3017"
Jump to navigation
Jump to search
(This behavior should be documented in caveats, not notes. I must have copied it from somewhere without reading it, as I couldn't make sense of it.) |
|||
| Line 2: | Line 2: | ||
{{#vardefine:caveats|{{#var:caveats}} | {{#vardefine:caveats|{{#var:caveats}} | ||
* When changing from a state that lacks a touch event into a state that has a touch event, the first touch will be dropped; this effects all three touch events ([[touch_start]], [[touch]], [[touch_end]]). | |||
<!-- | |||
* If the [[state]] is changed within either a [[touch_start]] or [[touch]] event, the [[touch_end]] event will not be triggered in either the source state or target state. See: {{Jira|SVC-3017}} | * If the [[state]] is changed within either a [[touch_start]] or [[touch]] event, the [[touch_end]] event will not be triggered in either the source state or target state. See: {{Jira|SVC-3017}} | ||
--> | |||
}} | }} | ||
}}<noinclude> | }}<noinclude> | ||
{{Box| | {{Box|Caveats|{{#var:caveats}}}} | ||
</noinclude> | </noinclude> | ||
Revision as of 20:46, 2 February 2010
|
|
SVC-3017 | A | Server drops first touch event when a script returns to a state with a touch_start handler |
Caveats
- When changing from a state that lacks a touch event into a state that has a touch event, the first touch will be dropped; this effects all three touch events (touch_start, touch, touch_end).