From 3107751fb79127c2495e0d7f7c097976fa4aad4f Mon Sep 17 00:00:00 2001 From: ahocevar Date: Thu, 10 Jan 2013 22:12:35 +0100 Subject: [PATCH] Clarifications on fallThorugh (see #829) --- notes/2.13.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/notes/2.13.md b/notes/2.13.md index 84eb0a68cc..dd3ca649a1 100644 --- a/notes/2.13.md +++ b/notes/2.13.md @@ -70,12 +70,7 @@ Corresponding issue/pull requests: ## Map property fallThrough defaults to false -The behaviour controlled by map property fallThrough wasn't consistent and changes -has been made to fix that. The change means that some events will fall through as -was intended with fallThrough set to true. Defaulting fallThrough to false after -this change is sensible in most situations and will probably be what most -applications expect, but if you previously relied on events beeing passed through -you will probably want to set fallThrough to true. +The behaviour controlled by map property fallThrough wasn't consistent (some events were swallowed even with fallThrough set to true) and changes have been made to fix that. Defaulting fallThrough to false after this change is sensible in most situations and will probably be what most applications expect, but if you previously relied on pointer or keyboard events being passed through you will probably want to set fallThrough to true. Behavioural change was made in this commit: