6 ms·

We have checked with one of the latest beta builds. In that build it didn't show the warning. It happens with the live chrome version. The issue is much more co

We have checked with one of the latest beta builds. In that build it didn't show the warning. It happens with the live chrome version. The issue is much more complex.

coverband 13y ago
On a Mac with current Chrome (Version 27.0.1453.116) hitting your sample dev URL, I don't get any errors at all...
- markshepard 13y ago
  It shows up now on Version 27.0.1453.116
- tteam 13y ago
  This specific instance in the screenshot has been fixed (this is the second time). Basically, in this specific instance if the "Login" button is changed to localize to a specific keyword "Connexion" as part of french translation, it shows up. No other keyword triggers it.. and no way to find out what the heck chrome wants. It is like playing proverbial whack-a-mole. Every update of chrome can potentially change their "heuristic" that thinks it has "found" a phishing attack.. and we have to scramble to see what the heck caused it and fix it. This would be funny if it wasn't so detrimental to a business. I will get the dev to recreate this on dev1 and post it.