tcfreder64@ Thanks for the update.

Able to reproduce this issue on Windows 10, Mac OS 10.13.3 and Ubuntu 17.10 on the reported version 69.0.3497.92 and latest Canary 71.0.3554.0.

Bisect Information:
===================
Good Build: 69.0.3494.0
Bad Build : 69.0.3495.0

By running the per-revision bisect script, runtime error was coming up. Hence below is the Changelog URL by running Chromium bisect.

https://chromium.googlesource.com/chromium/src/+log/f51aa161518f69211d222fcfb61691b9c9138d05..d792fdacbca87dd9bf361c6e99b51d21d5f2b497

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1138238

rhalavati@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding 'ReleaseBlock-Stable' for M-69 as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks..

+msramek for sanity check.

I think the behavior is as expected. Since Flash permission is no more stored, the 'add' button is removed and users can only give permission to a website for the current session.

That is correct. Flash permissions are now non-persistent, and thus not really "settings" to be configured in advance. We removed the [Add] button to avoid having users spend time manually configuring something that will soon be reset anyway.

This is WAI.