Sure I will check it out when I get a chance.

This fails because the above website redirects to www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash

That's a URL pattern that doesn't match any of our existing regexes. We can add it, but there's an additional problem:

The permission prompt still doesn't show up for some reason. Maybe because I see another (IFRAME) navigation that follows the above navigation to:

https://accounts.google.com/o/oauth2/postmessageRelay?parent=https%3A%2F%2Fdoubleclick-elearning.appspot.com&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en.UVv6tAUEHFA.O%2Fm%3D__features__%2Fam%3DgQ%2Frt%3Dj%2Fd%3D1%2Frs%3DAGLTcCMZ6W_qROBknxsxCzY952qc90wWyw#rpctoken=793085321&forcesecure=1

Do subsequent navigations cancel triggered permission prompts?

You can repro with my patch here: https://codereview.chromium.org/2699993002/

Also - it may just be easier to ask the reporter to update the above site to using SWFObject 2.0 and try using a simple link instead of an auto-redirect.

> Do subsequent navigations cancel triggered permission prompts?

Yes subsequent navigations across pages will cancel existing prompts.

> Also - it may just be easier to ask the reporter to update the above site to using SWFObject 2.0 and try using a simple link instead of an auto-redirect.

If that seems like a better approach, I'm ok with that too.

(Thanks for taking a look at this :)

Marking wontfix, because problem seems isolated, and it's better to ask site maintainer to update to SWFObject 2.0.