Originally Posted by Larry-NC
Me too, but then it switched to "Sorry, you have been blocked!" and won't post at all.
Looks like some software developer rolled some "innocuous change" into Production without testing first. Unfortunately, happens all too often.
Or it might just relate to the Chrome update I installed yesterday. Who else is using Chrome?
I think those are called "unanticipated consequences", rather than coding errors. (Expecting to never have a problem is unrealistic.)
I'm using Edge, based on Chromium. I'm not having the problem. I experienced it once or twice in the past couple of weeks but attributed that to a poor connection causing mouse click errors.