My bug may have a different cause, as downgrading to Chromium 43.0.2357.73 restored correct behavior.