From 016a1907e173356ac0e4efe7728915656df793e0 Mon Sep 17 00:00:00 2001 From: Ben Alpert Date: Fri, 7 Aug 2015 13:33:42 -0700 Subject: [PATCH] Disable event.path handling Looks like #4558 isn't ready yet and we'd like an interim fix. --- .../dom/client/ReactEventListener.js | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/src/renderers/dom/client/ReactEventListener.js b/src/renderers/dom/client/ReactEventListener.js index b2d328e3b90..ea22e29e8a9 100644 --- a/src/renderers/dom/client/ReactEventListener.js +++ b/src/renderers/dom/client/ReactEventListener.js @@ -62,13 +62,18 @@ PooledClass.addPoolingTo( ); function handleTopLevelImpl(bookKeeping) { - if (bookKeeping.nativeEvent.path && bookKeeping.nativeEvent.path.length > 1) { - // New browsers have a path attribute on native events - handleTopLevelWithPath(bookKeeping); - } else { - // Legacy browsers don't have a path attribute on native events - handleTopLevelWithoutPath(bookKeeping); - } + // TODO: Re-enable event.path handling + // + // if (bookKeeping.nativeEvent.path && bookKeeping.nativeEvent.path.length > 1) { + // // New browsers have a path attribute on native events + // handleTopLevelWithPath(bookKeeping); + // } else { + // // Legacy browsers don't have a path attribute on native events + // handleTopLevelWithoutPath(bookKeeping); + // } + + void handleTopLevelWithPath; // temporarily unused + handleTopLevelWithoutPath(bookKeeping); } // Legacy browsers don't have a path attribute on native events