This should be fixed with #3.
Requesting merge, as we'd like this for M67. The original patch made the branch cut, but was reverted for a compile conflict with revision fef93a84a5b56945d02cada97f4ec886ae34c0e2 (which has since been resolved).
This bug requires manual review: Reverts referenced in bugdroid comments after merge request.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
@6 It seems to look good in Canary so far - no reports of crashes. The patch looks large, but isn't that big - particularly in terms of production code (the vast majority is test-only). It is desirable to merge back to 67, particularly given how early we are in the cycle (and that it originally made branch cut before being reverted for a collision).
Turns out this merge isn't required.
Original patch landed in revision 550426.
M67 branched at revision 550428.
The patch was reverted in revision 550482.
So, the patch is already in M67. Removing merge labels.
Comment 1 by bugdroid1@chromium.org
, Apr 13 2018