I'm not sure why you have posted this in the SafeZone Browser sub-forum as the SafeZone Browser is based on the chromium base, it isn't Google Chrome.
A security article from January 20th 2016 is pretty old in security terms. Given this is Google Chrome, I would say this is likely a squashed bug now.