862802 - Browser does not remember "Always do this..." plugin choice when viewing local files

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[RB]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130409194949

Steps to reproduce:

1. View a local web page that contains Flash content.
example: file:///C:/MyFolder/bin-debug/Viewer.html

2. Click the red plugin icon next to the address bar.

3. Click the pull down menu and select "Always activate plugins for this site".

4. ( Nothing happens )

4. Click "Activate All Plugins".

5. The Flash content plays.

6. Reload the page (exact same local URL), or open a new tab with same URL, or open new browser with same URL, etc... In other words "view the same site"




Actual results:

The "Click to Activate" state appears again and user must make activation selections again even though they selected to "Always activate all plugins" for that URL.


Expected results:

The browser should have remembered the preference for the URL, even though it was a local file.

WHY IS THIS IMPORTANT?
At our company, we developers test Flash content dozens, if not hundreds of times a day. The plugin activation steps impact our efficiency.

WHY DON'T WE JUST UPGRADE THE PLUGIN?
Our software is made for kiosk installations and is designed with Flash Player 11.3 as the target player. We have a "code freeze" (AKA "version freeze") at 11.3 to prevent unforeseen bugs and issues resulting from changes Adobe decides to make. We cannot just blindly upgrade as that would cause dozens of completed software products to go back into QA for sanity tests and potential bugs can and do appear.

So for us guys who do local testing, can you put in a setting somewhere to allow us the CHOICE of how plugins behave? THanks.

Comment 1

[Michelle Funches - QA]

@Reporter: Please confirm this is fixed for you.
If it is not fixed, please state your current operating system and Firefox version.

Comment 2

[Michelle Funches - QA]

Closing this as incomplete due to inactivity and lack of response from the
reporter. Feel free to reopen the bug if the issue still reproduces on a
current build.