I've been developing some custom visuals. I have a "debugger;" statement at the top of my constructor and update methods, and I've been successfully using that to follow execution using F12 tools in IE11 and Chrome. But today, the browser doesn't pause when it reaches the debugger statement - it continues as if the F12 tools aren't open.
I not sure what could have changed this behaviour.
What can cause this? How can I get the old behaviour back?
Some things I've tried:
- I have freshly rebooted my computer.
- I've tried searching through the source in the F12 tools for "debugger" to see if I can find my code. But I can't find it.
- Power BI is definitely using my developer visual. If I stop the "pbiviz start" process, then Power BI shows the "Can't contact visual server" warning. When I rerun "pbiviz start", the visual comes back.
- In the F12 tools network tab, I can see that my visual.js code is being loaded.
- I tried adding a console.log('update') call at the top of the update method, just before the "debugger;" line, but I don't see this word appear on the F12 console, either in Chrome or IE11. This used to work, can't understand what's changed now.
- When I run in Chrome, the console doesn't show anything interesting.
- When I run in IE11, the console does show some errors. I think it always used to show some errors, but they didn't seem to cause any real problems in the past. It now shows
SCRIPT5: Access is denied.
File: visualSandboxMinimal, Line: 1, Column: 1
- When I refresh just my visual in IE11, in the console I see various notes about CORS and webanalytics, but also the following three errors. If I recall correctly, they were there even when the debugger was working correctly.
SCRIPT70: Permission denied
File: powerbiportal.common.bundle.min.js, Line: 50, Column: 21893
SCRIPT70: Permission denied
File: powerbiportal.common.bundle.min.js, Line: 50, Column: 21893
SEC7120: Origin about: not found in Access-Control-Allow-Origin header.
File: about:blank