Important: when posting, please provide your Club Number at a minimum, and as many details as possible.
For further info, please read This page before posting.

Closing Contact Us form loads home page in Chrome

  • Stephen Keilholz
  • Stephen Keilholz's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 3
  • Thanks: 1

Closing Contact Us form loads home page in Chrome

7 years 6 months ago
#71735
Greetings,

I use Google Chrome (current version, 68) as my primary browser and found that, when I close the Contact Us form, regardless of what page I am currently displaying, the Home Page is re-displayed.

An example of how to reproduce:
  • Click on the Club Calendar page
  • Click on Contact Us
  • Click on the Close button in the dialog box, (or the X button, both exhibit the same result).

I attempted to reproduce this in Internet Explorer (11) and found that the issue does not appear there. I don't commonly use other browsers.

I was planning on linking to the Contact Us form from another page but I believe users might find it disconcerting if the page they are viewing is changed.

[size=125%]Stephen Keilholz[/size], CC
RIEL Toastmasters (586030)
Sergeant at Arms (2018-2019)
[size=125%]Stephen Keilholz[/size], CC
RIEL Toastmasters (586030)
Sergeant at Arms (2018-2019)
The topic has been locked.
  • Brian
  • Brian's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 11377
  • Thanks: 3723

Re: Closing Contact Us form loads home page in Chrome

7 years 6 months ago
#71742
Using Chrome, I tried opening and closing your contact form on many pages even submitted one. It never refreshed to the home page.
Thank you,

Brian McDonald DTM
Silver and Wiser Online Toastmasters Club #777940

Technical Support Consultant for FreeToastHost
The topic has been locked.
  • Stephen Keilholz
  • Stephen Keilholz's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 3
  • Thanks: 1

Re: Closing Contact Us form loads home page in Chrome

7 years 6 months ago
#71746
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!
[size=125%]Stephen Keilholz[/size], CC
RIEL Toastmasters (586030)
Sergeant at Arms (2018-2019)
The following user(s) said Thank You: SteveTheTechie
The topic has been locked.
Moderators: BrianHeniPamrhtaylor3marc33NotLiableNSBjgavinLcala305peterb323DebbieT
Time to create page: 0.144 seconds