03-10-2016, 01:35 PM
Tested on Chrome 48/49, also has this issue. So it may be a bug of Chromium.
Maybe they change the behavior intendedly.
We will have a research at this issue.
Maybe they change the behavior intendedly.
We will have a research at this issue.