Mine too. The habitually responding posters will tell you "try another browser, clear cache and cookies, etc" None of which have worked for me either. When the host site creates a problem for us, it is the host site's responsibility to correct that item which is 75% of the time an unintended result of a programming change that was not properly planned or researched to prevent interference with other subroutines. The problem is that without proper change management planning and step by step checks, the programmers usually have no clue of where to start and they too ask end users to try these same steps to solve a problem that we can neither solve nor are responsible for. I started in computer support 52 years ago with a major international company and statistics will show that far in excess of 50% of all failures in the past 50 years are a direct result of a programming missstep, not a hardware or end user issue.
