Antonin Hildebrand

To keep the ball rolling, I have just tested ExceptionInfo behaviour[1]. Currently cljs-devtools has pretty nice behaviour, it presents the error printed with IPrintWithWriter protocol[2]. The implementation is questionable because...

btw. here is how it looks currently: 

Actually this `ExceptionInfo` is not a fully working CLJS type, so cljs-devtools do not treat it correctly under all circumstances. I went down the rabbit hole and proposed a solution...

Thanks for reporting. My wild guess is that this will be related to some weird CSS interaction between cljs-devtools markup and official DevTools stylesheets.

I investigated it and my conclusion is following: 1. it is a CSS issue, caused by `overflow:hidden` rule defined on some parent DOM nodes in "object properties" section and the...

After further investigation. The overflow is triggered when scope area is small enough to fit whole custom formatter content. Display of disclosure triangles, seq numbers or "fn" markers is just...

Filled upstream as [bug 1004070](https://bugs.chromium.org/p/chromium/issues/detail?id=1004070).

I'm with you. That is why I recommended them to get rid of that `overflow:hidden` logic and let the content scroll horizontally instead.

Interesting observations. But I'm sorry I'm not going to investigate it. Currently each release of cljs-devtools performs following dead-code elimination sanity check: 1) compiles a trivial empty project with `:dependencies`,...

I was curious. I have [just added](6ac5431ccadb58a4418fbd4f81f7f6c54200e2cd) some helper scripts to compare DCE in scenarios you described. You can run `lein compare-dead-code` or `lein compare-dead-code-with-pseudo-names`. My output looks like this:...