The line/column properties also need to reflect the location in the sourcemap file

swrobel@ - Thanks for filing the issue...!!

Could you please provide a sample url/test file to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!! 

I'm having a really hard time putting together a repeatable test for this. I observed the issue when using Selenium to drive headless Chrome but it's a complex test case from my application. Is there a simple tool you recommend that will simply let me stream logs from an arbitrary page? What about a test page for sourcemaps that generates output to logs?

This is the best tool I've found but it requires user interaction to produce console logs: https://mdn.github.io/devtools-examples/sourcemaps-in-console/index.html

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue seems to be out of scope for triaging as this is related to Headless (as per comment#4), Hence adding appropriate label and component. Requesting someone from respective team to have a look into this issue for further triaging.

Thanks!

This is not only a headless issue. You can launch Chrome in interactive mode with  --remote-debugging-port=9222 and experience this same behavior.

You can use Debugger domain to sniff for sourceMapURLs for all parsed scripts. logEntry would point to a scriptID and you would get the sourceMapURL.