This is a regression issue broken in ‘M-71’ and below is the manual bisect information:
Good Build : 71.0.3568.0 (Revision : 595545)
Bad Build : 71.0.3569.0 (Revision : 596015)

Change Log URL :
https://chromium.googlesource.com/chromium/src/+log/71.0.3568.0..71.0.3569.0?pretty=fuller&n=10000

Suspecting : r595953 ? 

Kyle@ : Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note:
1. Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message for above range. (tried on other machines but still getting the same error again)
2. And this issue is not reproducible in 'Chromium builds', hence provided manual suspect through 'Change log'.
3. Able to reproduce this issue in Mac(10.12.6, 10.13.1, 10.14.1, 10.13.6) and Linux(14.04 LTS) OS with Canary build #71.0.3569.0

Thank you..!

marking as RBS, please change if required

Yes, it looks like https://crrev.com/c/1255600 broke the old UI. That UI will no longer exist in 71+ so this should fix itself.

Kristi - are you planning to remove the md icons and custom link flags before branch?

Ramya - I think we'll need to turn on the new ui for 100% on the remote ntp for 71+, currently it's only 98 or 99? we can probably just modify the 'all features' param to only depend on the chrome version

c3: Yes, I'll be pushing a change for that soon.

We want to continue to run with a 1% holdback in order to collect more data. While it's possible this might be over by M71, it's not guaranteed.

Reverted the change here: https://crrev.com/c/1265024. We'll wait until M72 to remove the old stuff.