+John Lauer, It looks like your my last hope. gurgle, gurgle, help please, gurgle, cough… 
Why is it such an issue to select the buffer algorithm manually?
What browsers and os do you use? I have not seen the issue that you report.
And lastly because this is all open source you can always fork the widget yourself and investigate+solve issues. Then issue a pull request or use the widget yourself if you don’t want to contribute for any reason.
touchpads are a nightmare when you are standing up. It’s very frustrating and time consuming to try to open the drop-up menu and keep it open while positioning the cursor in the garage. You’re giving me the ultimatum to live with it or learn programming then fix it myself and send the code to you. This seems to be a recurring attitude in the open source world. It’s not just you.
No ultimatum. There is limited resource to develop and I’m not hearing a compelling argument as to why this should be booted up the list. Particularly since I’ve spend 90 minutes searching the code for bugs and I cannot repeat the error (and this is not even my code).
If you have the error and you feel it is important to fix or enhance it then the best way you can repay people for having developed the application to date is to participate in its development and pay it forward. Your choice if you don’t.
Chilipeppr suffers similarly to most general webapps with not being touch optimised. I see this daily as I use a lot of cloud services in my career as a lawyer. This is a limitation of browsers rather than with CP. There is a cp tablet workspace however. That may serve your needs better although I am not sure whether it is grbl compliant. If you go that route and don’t wish to create your own workspace then perhaps the answer is to buy a tinyg.
I would have never guessed 90 minutes by reading your earlier post. Thank you for your efforts. I appreciate it. What version of GRBL and SPJS are you using that work correctly?
What version of SPJS do you use? And what revision GRBL?
Spjs 1.86 and 1.94. Grbl 0.9j and 1.1e
Neither are relevant to the issue with chilipeppr that you report. That is most likely to be an os/browser specific error or something in your settings preventing the establishment of local cookies.