Open AllanWang opened 5 years ago
I have the same issue, on Mojave. Seems like its only on Chrome. Safari works fine
Ok so it seems like the issue is full screen mode on the browser that is preventing the debugger from working correctly.
OS: MacOS High Sierra Browser: Safari, Chrome, Chrome Canary Apps: elm-spa-example, create-elm-app
On all 3 browsers and on both apps it works fine as long as you are not in full screen mode in that browser.
I think it is an issue because if you are in full screen, it puts the debugger into a new tab.
When you are not in full screen it opens a new browser window and this works perfectly.
@Pilatch @evancz
I would love to look into this more, as I have submitted a pull request for the debugger, but I think the way Evan does things in Elm core is on his own. Or he does batch processing of issues. So I'm not seeing a lot of motivation for me to make additional contributions until there is some evidence that effort is not wasted.
Finally found this issue after battling this for ages, thanks for filing it (and thanks to the commenters)! Kinda surprised this is still happening 3 years later, is it uncommon to run the debugger fullscreen?
In case it's helpful for reproducing this:
My current setup is Nixos+Xmonad, so the elm debugger automatically launches into fullscreen (on top of the browser window hosting the app itself). This reliably causes the debugger to ignore clicks every time (it seems it also causes an issue with clicking messages in the message list). Switching layout of the debugger+Chrome side-by-side makes the debugger respond to all mouse clicks again.
Beyond the freeze in the main view as mentioned in #16, I can't seem to click anything when accessing the debugger:
Clicking the dropdown arrows, or any item in the left list does nothing. I just started learning elm so I'm not sure what the expected behaviour is, but I assume we should be able to see the full model correct?
I've set this up by using
create-elm-app
. Snapshot of my projectUpdate:
It seems like the problem occurs on my MBP, with Mojave. It works fine on my other laptop with Kubuntu. Both are using Chrome