Yeah. Debugging these things are not fun. Chrome also allows you to set breakpoints on DOM elements.
I’ve found this useful in breaking at a specific place in the lifecycle to see what’s going on. > On Mar 3, 2017, at 7:24 AM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/2/17, 8:51 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote: > >> I will try to fight with this. The problem is that in this case I don't >> have >> any exception in the console. :) > > Yuk. I think I would next examine the DOM. Compare it against the > js-debug version. If DOM objects are missing in js-release, then I would > set breakpoints where they are created. > > HTH, > -Alex >
