After the defeat in the first T20I in Delhi, India had their task cut out when they took on Bangladesh in Rajkot. The Rohit Sharma-led side came back strong with the captain leading from the front with a match-winning 85-run innings. India after opting to bowl first restricted Bangladesh to 153 for 6 and then chased it down in just 15.4 overs with 7 wickets hand. Rohit top-scored with a 43 ball 85 laced with six sixes and six fours. Apart from Rohit’s free-flowing batting, the biggest talking point of the match was Rishabh Pant.
ALSO READ: ‘Winning is the priority, but...’ - Rohit Sharma outlines philosophy
The incident happened when Yuzvendra Chahal came on to bowl in the 6th over of the Bangladesh innings and hit his stride immediately. The third ball of the over was a beautifully tossed up delivery, Liton came down the track and attempted a cross-batted slog across the line of the delivery, but missed the ball as it spun away. Rishabh Pant collected the delivery and whipped off the bails. The umpire, however, referred it to the third umpire who saw different angles and gave the batsman a reprieve as replays showed that Pant had made first contact with the ball in front of the stumps - and hence, the ball was called a no ball.
Here’s what the MCC LAWS say:
{{/usCountry}}Here’s what the MCC LAWS say:
{{/usCountry}}27.3.2 In the event of the wicket-keeper contravening this Law, the striker’s end umpire shall call and signal No ball as soon as applicable after the delivery of the ball.
27.3.1 The wicket-keeper shall remain wholly behind the wicket at the striker’s end from the moment the ball comes into play until a ball delivered by the bowler touches the bat or person of the striker or passes the wicket at the striker’s end or the striker attempts a run.