Using the per-revision bisect providing the bisect results,
Good build:61.0.3162.0(Revision:488073).
Bad build:61.0.3163.0(Revision:488528).

You are probably looking for a change made after 488135 (known good), but no later than 488136 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/1c955f0530f6fe3f0f5bfdbe071d0c680a615b99..830b21927c2ad4ad9982d4b261d4eb3d4ab68451

From the CL above, assigning the issue to the concern owner

@paulirish : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Reviewed-on: https://chromium-review.googlesource.com/576359
Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.5 and Able to reproduce in latest Canary #61.0.3163.0
Adding Release Block-Stable for this issue.Please remove if not the case.

Known issue, but sure I'll fix this. :)

Thanks

 paulirish@ would be nice to have the fix sooner(before Beta launch) if possible for better coverage during M61 Beta.

URGENT - PTAL.
Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the M61 branch #3163 ASAP to have enough baking time in Beta before Stable promotion. Thank you!

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label.

Still able to reproduce the issue on Ubuntu 14.04 using latest chrome version 62.0.3179.0

paulirish@ Could you please look into this issue as it has been marked as a stable blocker.

Thanks!

[Bulk Edit]
URGENT - PTAL.
Your bug is labelled as M61 Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP.

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label.

Thank you.

We're comfortable shipping with this. I'd like to fix it but it doesn't block stable.

Irish, mind if I take a look at fixing this one today? Seems simple enough to knock out pretty quickly. It just needs a conditional render.

So, conditional rendering on this is difficult since the select box basically needs to exist as things are currently done. Since the main problem is that it is *empty*, perhaps we can tackle this a different way.

Let's have a default option that says, "Perform an audit" that will be removed when the first one is inserted. That way it isn't entirely empty and the node is in place for use once an audit item is added.

Sound good?

And here is a patch file of what I'm thinking will work. Just let me know if this is an acceptable resolution and I'll update my Chromium pull and submit a request for it.

Deleted: default-option.diff 1.5 KB

default-option.diff 1.5 KB Download

Audits panel UI was redone in https://chromium-review.googlesource.com/c/chromium/src/+/1058708

This bug has now been fixed.