Brian,
Thank you for your quick reply. I went ahead and did some additional testing and found that the chrome setting (in chrome://flags)
Latest stable JavaScript features, when enabled, caused the situation I was seeing. When disabled, I could not reproduce the problem.
The text describing this setting is:
Code:
Some web pages use legacy or non-standard JavaScript extensions that may conflict with the latest JavaScript features. This flag allows disabling support of those features for compatibility with such pages
I'm not sure if the setting I had is the default setting or one I customized sometime in the distant past.
Regardless, Unless you get more complaints about this, I consider this issue to be understood and not one that might gate using the Contact Us link from other pages.
Thanks again!