Yeah, the risk is already high enough.
Web site owners should have enough time to test the removal of /deep/ using Chrome Canary or M60 beta, but we have not been able to provide this opportunity for these 2 months, blocked by CrOS.
Given that, I propose that we should push this back to M61 or M62. Let me decide it soon, and announce it, and update chromestatus. I need time to analyze the risk after I can get all information from CrOS team.
Maybe we should have a postmortem for this confusion. I had a private discussion with alemate@ and rkc@ in the last week, and I have asked them to update the progress many times. I don't want to see that this kind of confusion would happen again in the future.
I assigned this back to you because dpapad@ mentioned here (https://bugs.chromium.org/p/chromium/issues/detail?id=719331#c43) that there were 4 other references to iron-flex-layout.html. I don't know if it safe to reland this change, hence leaving it up to your judgment.
Comment 1 by candr...@chromium.org
, May 17 2017