I saw this and thought the exact same thing! Super excited to test it out upon release.
The other nice thing about FF for devs is that Chrome is a little too robust sometimes. I've had some egregious errors in my markup and Chrome still manages to do what I intended. But then it's broken on every other browser.
As far as I've experienced, anything that runs perfectly in FF runs perfectly in Chrome. But the reverse is not true.
They should both be using the html5 parser now, so "errors" should be well defined rather than browser dependent. Could be a bug in the implementation.
The other nice thing about FF for devs is that Chrome is a little too robust sometimes. I've had some egregious errors in my markup and Chrome still manages to do what I intended. But then it's broken on every other browser.
As far as I've experienced, anything that runs perfectly in FF runs perfectly in Chrome. But the reverse is not true.