There is now a Chromium bug for this issue:
Please star the bug report in order to raise its priority.