Thanks for the report.  DevTools tries to hide the column number only when it can linkify the url and bind it to a script in the Sources panel.

To repro, I've made a small jsfiddle that produces similar output:
http://jsfiddle.net/r9gedms4/

In your stackTrace, can you confirm that clicking on the urls on each line will jump to the correct column number in the source file?

Yes in Chromium 57 everything works as expected. The devTools jump to the right column and if i unminify the stackTrace with sourceMaps and "https://www.npmjs.com/package/retrace", everything works fine.

In your jsfiddle is the column number given also works in the current google chrome 67. But the minified version with thousands of columns not.

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

i checked it again, and if i click on the wrong "link text" the dev tools jumps to the right column (like given in chromium 57). so i think only the link text
"(cmweb-core.js?v=3492:1)" is wrong and misses the full url with column.

Okay, so to clarify:
- Clicking the links reveals the source code at the correct column position
- You would like some way to view/copy stack traces that includes the column numbers

I think we can try to include the column number when copying a stack trace, similar to how copying a truncated link with '...' copies the full text.

I send the stackTraces with "onunhandledrejection" and "onerror" to the server and handle them later. So inject the column number only in on copy will not work for me. 

I think the devTools and the console are written in html and javascript and the link are anchor tags with the correct href attribute (with column number) so the solution is to use the href as link tags. Or am i wrong?

The functionality was correct in chromium 57 and whatever has been changed must have a reason or it is a bug and has to be reverted.

When you have an Error object, it's .stack property has column numbers. That's what you can use for automatic stack collection from production.

In DevTools UI, we do not show column numbers most of the time because it's just extra noise. When debugging unminified source, line number is usually enough. Even when dealing with minified source (which is not an intended way to debug your application), showing ":1833909" to the user doesn't add any user-readable information.