cross-browser innerhtml fixes

[Abazhenov]

Fixes some tests that were failing when running browsers other than google chrome.

Some tests were failing because where chrome would render: <input class="foo" id="test">
Firefox / safari / edge might render: <input id="test" class="foo">

This PR uses our innerHTML utility to fix those tests and ensure that the strings we are comparing rendered components to correspond to what they would be in the browser running the tests.

This only addresses compatibility issues that have to do with comparing HTML strings.

[trueadm]

CCing @Havunen @nightwolfz @LukeSheard for review

[trueadm]

Thanks @Abazhenov this is great stuff! :)

Have you tested that all tests pass on npm run test and npm run browser?

[trueadm]

Meh, the Travis build failed due to an NVM issue..

[LukeSheard]

I think you forgot to commit the tools file / import it from some of the tests. But otherwise this looks great!

[Abazhenov]

All tests are passing on my end

[Abazhenov]

@LukeSheard OK I'll look it over, innerHTML was already defined in src/tools/utils on line 11, also, some files already had it imported prior to my changes.

[Abazhenov]

@LukeSheard hopefully this is more clear, innerHTML should be required in all the files that need it

[LukeSheard]

Okay. I'm only on some app my iPhone so this isn't a proper review. Thanks!

[LukeSheard]

I'm quite happy to merge this, but we should add a chore issue to tidy up all instances of testing HTML strings with ...innerHTML).to.equal('${STRING}') to use the innerHTML compare. I'll merge this and open an issue.