On Sat, Apr 16, 2016 at 7:56 PM, Gerald B. Cox <gbcox@bzb.us> wrote:
It appears to be an issue with the current chrome-unstable (51)... it looks good on chrome-stable.  I'll file a bug report with chromium so they can hopefully fix it before 51 goes stable.

Bug report is here:  https://bugs.chromium.org/p/chromium/issues/detail?id=604171