• Welcome to the Cricket Web forums, one of the biggest forums in the world dedicated to cricket.

    You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join the Cricket Web community today!

    If you have any problems with the registration process or your account login, please contact us.

**Official** South Africa in England 2012

Jayzamann

International Regular
Seriously though, every now and again is accidental, but doing it three or four times in your opening spell, having a batsman complain about it. That's dead ball territory.

The thing here is that it was also a wicket taking ball. Therein lies the controversy.

ed: I'd probably be spitting chips if this was called against an Australian bowler.
 

Jono

Virat Kohli (c)
So did Nasser just shut all you people down by reading the rules, or is the fact the umpire didn't call it earlier still an issue?

Didn't see the previous balls. Ultimately the umpire can decide if the batsmen was distracted and its their discretion.

Controversial call either way.
 

Spark

Global Moderator
So did Nasser just shut all you people down by reading the rules, or is the fact the umpire didn't call it earlier still an issue?

Didn't see the previous balls. Ultimately the umpire can decide if the batsmen was distracted and its their discretion.

Controversial call either way.
That's my issue.
 

uvelocity

International Coach
Then he should do it every time. Inconsistent application of laws is the worst kind of umpiring.
it happens sometimes. when it's rare its just something that happens, oh well (and hurts your knuckles too unless you're huckleberry) doing it constantly is too much. I was about to post it was annoying
 

Thriel

Banned
From Cricinfo: Spike says: "I believe the umpire had spoken to him about this during the other two instances, and the umpire had already made up his mind that the next time this happens it would be a dead ball."
So what is the problem then ?
 

Spark

Global Moderator
Its not so cut and dry. This is similar to running on the pitch. Fine to give a warning first imo.
When you run on the pitch, the established protocol is to give an official warning. Not just some ad hoc interpretation of a law when you feel like it.
 

Viscount Tom

International Debutant
Its clearly not distracting because they're managing to hit some for four when he hits the stumps.

Bit shocking umpiring tbh.
 

Jayzamann

International Regular
To be honest, this happened a few times to me when playing and it wasn't distracting in the slightest. I have a feeling for most umpires they don't consider knocking over the stumps at the nonstrikers to be a distraction either.

But when a batsman says to an ump that it is distracting...
 

Prince EWS

Global Moderator
I honestly just think it's overly harsh to deem that "distracting" unless he's doing it on purpose. I'd be saying the same thing even if he didn't take a wicket with it. That's not what their law is there for; it's an outrageous call IMO.
 

Spark

Global Moderator
To be honest, this happened a few times to me when playing and it wasn't distracting in the slightest. I have a feeling for most umpires they don't consider knocking over the stumps at the nonstrikers to be a distraction either.

But when a batsman says to an ump that it is distracting...
Never heard a word about it during the fifty times it happened during the Aus ODI series either, and one would've thought the bats would've had every reason to complain...

EDIT: In fact I'm pretty sure he took a wicket off one, and the batsman just walked straight off.
 
Last edited:

Top