Regression: No Flash Pop-up asking for permission on new sites
Reported by
frnkprn...@gmail.com,
Jul 5 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Example URL: http://get.adobe.com/nl/flashplayer/about/ Steps to reproduce the problem: 1. Go to chrome://settings/content/flash and make sure these settings are set to the default. both "Accept that sites use flash" and "Ask first" need to be enabled. Make sure the example domain does not exist on the whitelist. 2. Open the example url. What is the expected behavior? Expected is that a pop-up appears asking if the site should be allowed to use flash. What went wrong? There is no such pop-up. On any site where you want to use flash you need to manually add it to the whitelist. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Unknown Does this work in other browsers? Yes Chrome version: 59.0.3071.115 Channel: stable OS Version: 10.0 Flash Version: 26,0,0,131 sadly, i am responsible for a legacy magento store which uses flash for the functionality to upload images. Over the past few days this functionality broke, and i had to manually whitelist the domain on my colleagues'chrome installations. All my collaegues had the newest version, three of them had the problem of no popup and no functioning flash. Weirdly another collaegue was able to fully use the funtionality, even after fully clearing her cache, cookies etc. All the involved chrome installations have the same build number and flash version.
,
Jul 5 2017
Sorry, i forgot to edit the title before posting. Can this be changed to the following? "Regression: No Flash Pop-up asking for permission on new sites"
,
Jul 5 2017
(Editting title as requested.)
,
Jul 7 2017
Unable to reproduce with Chrome 59.0.3071.115 on Windows 7,10, Mac and Linux.
,
Jul 11 2017
Unable to reproduce with chrome 59.0.3071.115 on Windows 10 and Linux at home as well. This seems to have been an issue with a deployed version of chrome in our business environment, and a new distribution of the same chrome version solves this problem. I think this is not a chrome bug, so this issue can be closed when nobody else can reproduce this. I am sorry i did not investigate further before reporting.
,
Jul 11 2017
Thanks for confirming. Closing per comment #5. |
||||
►
Sign in to add a comment |
||||
Comment 1 by frnkprn...@gmail.com
, Jul 5 2017