This fix has made it into Canary and I've verified that Canary now passes the relevant web-platform-tests.
I'm requesting merges to M53 and M52, as per discussion in https://groups.google.com/a/chromium.org/d/msg/blink-dev/KmpKQhweJQY/K1q07xDSAQAJ
In summary, this is a fix to a new feature (with likely low usage) to bring Chrome's implementation into compatibility with Firefox and the spec.
M52 is already in Stable for Desktop and bar is VERY high.
If change is well baked in canary, safe to merge and critical for M52, then only we can take it for M52. Could you please confirm it is a safe merge and important for M52?
The change just changes a single character in an IDL attribute, and doesn't touch any (non-generated) code. So it should be a safe merge. As for importance, since this is a new feature, we suspect there is very low usage currently but developers will be starting to use it soon, so we would really like to avoid a bunch of code getting shipped in the next few weeks that is subtly incompatible with other browsers.
Comment 1 by est...@chromium.org
, Jul 19 2016