Note that in order to launch a survey, and not get multiple support call from users. I have added the following to the custom.css to hide the issues.

.fruity .alert-danger {
background-color: #fff;
display:none;
}

.fruity .clearall-saveall-wrapper {
display:none;
}

I was getting the clear-all - resume later dialog even though this is disabled in the admin for users.

So this was really problematic, and although it solved somethings, was still get error reports. As this is a live system, I have rolled back the Update to 5.6.32+ 230731
There is definitely something not quite right. Sorry, I was hoping I could leave it in place till the ticket was picked up.

I do have backups of all the files if anyone want to take a look, but im guessing this isnt an isolated issue.

Did you make some changes on theme?

Using fruity theme on 5.6.33 I am seeing this (image1). Looking at the same piece of code I am seeing this (image2), specifically ".js .ls-js-hidden" on line 5 of survey.css instead on line 22 in my case.
Another thing that I see from image2 is that there are 2 different css theme files loaded (sea_green and sunset_orange), for me this is not the case if I use one or the other.

I don't see any javascript disabled message on your or newly created survey (tested with Chrome and Edge).

Thanks for having a look. The reason you could not see the error was as mentioned I rolled back to 5.6.32. Interesting spot regards the sea_green css. This is not something I have played with.
The theme was a fairly simple Extend to the Fruity - with some fairly minor cosmetic changes (backgrounds, overlays font sizes etc)

I had a look through the entire extended theme and the only place I can see sea_green.css is within the config.xml file (same in the stock fruity template). So interesting but don't think this has a bearing to my issues.

However, just noted that there has been another update to 5.6.34 - so rolled that to a test system - The problem has gone away. Nothing listed in the changes that I feel would have created this, but for now, it has been solved.

Can anyone else shed any light as to why the sea_green css is loaded when the sunset orange is the one selected?

Also: Will post the link to the stage site version in a Private PM