Just tested again with the latest trunk (revision 990), and the bug isn’t there anymore.
Somewhere between chromium 42.0.2305.0 and 42.0.2311.11 the issue was fixed.
Just tested again with the latest trunk (revision 990), and the bug isn’t there anymore.
Somewhere between chromium 42.0.2305.0 and 42.0.2311.11 the issue was fixed.