Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit 0bcace3

Browse files
Carlo s A. Guillenbtford
Carlo s A. Guillen
authored andcommitted
docs(ngClick): improve style
1 parent 46c9c94 commit 0bcace3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/ngTouch/directive/ngClick.js

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,9 @@ ngTouch.directive('ngClick', ['$parse', '$timeout', '$rootElement',
9494
// encapsulates this ugly logic away from the user.
9595
//
9696
// Why not just put click handlers on the element?
97-
// We do that too, just to be sure. The problem is that the tap event might have caused the DOM
98-
// to change, so that the click fires in the same position but something else is there now. So
99-
// the handlers are global and care only about coordinates and not elements.
97+
// We do that too, just to be sure. If the tap event caused the DOM to change,
98+
// it is possible another element is now in that position. To take account for these possibly distinct elements,
99+
// the handlers are global and care only about coordinates.
100100

101101
// Checks if the coordinates are close enough to be within the region.
102102
function hit(x1, y1, x2, y2) {

0 commit comments

Comments
 (0)