Open rmescandon opened 7 years ago
and it would be nice if the Connect button could log the onClick all the way to journal (with the standard prefix: "== wifi-connect MSG").
Later: since we will only have one connect button, this issue seems to go away: that button does call the go backend handler which does log a Connecting msg: https://github.com/CanonicalLtd/UCWifiConnect/blob/master/server/handlers.go#L107
Management portal shows a connect button that when pressed, shows an alert informing of consequences of trying to connect, with an Ok to confirm. This implies pressing two different buttons to finally execute one single task. Let's permanently display the current warning text just above the button to connect.
Also, let's delete the separate connecting.html template and show the connecting message in the current page before calling the go backend that brings down the wifi-ap and attempts to connect. It's another bug that sometimes that connecting page does not even show.