The reason for doing this is that, under Chrome, you will encounter StaleElementReferenceException if the action changes the page. For example, entering a username may trigger the "not available" error to show, which selenium recognises as WebElement changed and throws the exception if it is accessed again.
Firefox doesn't do this, because it's not as strict.