UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:54.0) Gecko/20100101 Firefox/54.0

Steps to reproduce the problem:
When using the dev tools and clicking on a target=_blank link, the new page opens without dev tools activated.

If you need to inspect what happens in the next page at the first load (meaning activating "dev tools" in the new window and refresh wouldn't satisfy the test), you need to modify DOM at the first step to follow the link in the same window (that has "dev tools" opened).

What is the expected behavior?
It would be great to be able to specify chromium to automatically activate the dev tools before loading any content in the new tab/window if the "source" window had the console/dev tools activated. 

What went wrong?
Nothing

Did this work before? No 

Chrome version: 61.0.3163.0  Channel: dev
OS Version: OS X 10.11
Flash Version: 

Sorry for fr-english ;)