Not an issue for our tests on firefox 28; however, once we upgrade to Firefox 42 (or later), a new wait condition is needed here. Otherwise, the content is not set because selenium's action chain is starting too early.
