no, no extra steps needed. Just opening the sample.
But you are correct. I can't reproduce here at home with Win 8.1 and Chromium 66.0.3359.181 either, nor with FF26.
But I'm sure about what I saw. Can I enable some logging in Developer Console that helps?
now it is also working for me on the system that previously showed the error (now using v12.0p_2018-08-25).
I'm not sure what happened there, perhaps it was something intermittent.
Comment