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.
I do wish it had better integration with the web console though. It just seems strange when you pop-up the web console tab to have a JS prompt for entering javascript directly above a Browser prompt for controlling the browser.
It'd be nice if you could just go into a javascript entry mode on the browser prompt itself and see the output appear in the web console. Even something as simple as adding a javascript command where the argument passed into the command is javascript would be useful (perhaps someone could create an add-on that does this)
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.