[#FP-41] Event on close of Security.showSettings() panel

Flash Player

Event on close of Security.showSettings() panel

Created: 04/04/08 12:42 PM Updated: 07/13/08 02:56 PM

Component/s:

ActionScript Events

Security Level:

Public (All JIRA Users )

Severity:	Usability Issue
Reproducibility:	Every Time
Discoverability:	High
Found in Version:	Flash Player 8 - 8_0_34_0
Milestone:	Flash Player 9
Affected OS(s):	All OS Platforms - All
Injection:	No
Steps to Reproduce:	« Hide Steps to reproduce: 1. Security.showSettings(); 2. Try and detect a close of this panel to be able to move on in application flow. Actual Results: There is currently no way to detect the close of this panel. For the flow of many applications using the camera and microphone it would be good to know when this panel closes. Expected Results: It would be great to either be able to listen for a close event on this panel, pass in a callback function upon displaying the panel, or have a reference to the panel itself to be able to register event listeners with it just like any other component. The flow of some applications require that you show the dialogs then react after either permission has been granted, microphone has been change, camera has been changed, etc. Workaround (if any): Currently the only workaround we have it to size the flash file to the size of the security panel and try to detect mouse movement when it closes on a component that would be shown below. This is extremely inefficient and unreliable. Show » Steps to reproduce: 1. Security.showSettings(); 2. Try and detect a close of this panel to be able to move on in application flow. Actual Results: There is currently no way to detect the close of this panel. For the flow of many applications using the camera and microphone it would be good to know when this panel closes. Expected Results: It would be great to either be able to listen for a close event on this panel, pass in a callback function upon displaying the panel, or have a reference to the panel itself to be able to register event listeners with it just like any other component. The flow of some applications require that you show the dialogs then react after either permission has been granted, microphone has been change, camera has been changed, etc. Workaround (if any): Currently the only workaround we have it to size the flash file to the size of the security panel and try to detect mouse movement when it closes on a component that would be shown below. This is extremely inefficient and unreliable.
Language Found:	English
Bugbase Id:	222147
Triaged:	No
Participants:	Brian Westphal, Edwin Wong, Kevin Green, Philippe Piernot and Todd Slaughter

All

Comments

Sort Order:

[ Permlink | « Hide ]

Todd Slaughter - [04/15/08 04:56 PM ]

This is classified as a bug but it looks to me like a feature request. Is this misclassified? Shouldn't "bug" mean that something that's already in Flash is working incorrectly?

[ Permlink | « Hide ]

Kevin Green - [04/16/08 09:22 AM ]

This was originally classified as a minor enhancement but was reclassified to be a bug. I agree that it can be considered a bug as it is something that should be in flash for proper functioning of applications that require the use of the camera/microphone.

[ Permlink | « Hide ]

Brian Westphal - [06/12/08 08:15 PM ]

Can we boost the priority of this issue please?

[ Permlink | « Hide ]

Kevin Green - [06/26/08 10:59 AM ]

This should be relatively easy to fix, can you please boost the priority of this as it would make a big difference for usability of the security panel in application flow.

[ Permlink | « Hide ]

Philippe Piernot - [07/13/08 02:56 PM ]

You can detect if the dialog box is open by performing the following operation insider a timer event:

////

var closed:Boolean = true;
var dummy:BitmapData;
dummy = new BitmapData(1, 1);

try
{
// Try to capture the stage: triggers a Security error when the settings dialog box is open
dummy.draw(stage);
}
catch (error:Error)
{
closed = false;
}

dummy.dispose();
dummy = null;

////

Tested on Mac and PC / Flash 9,0,124,0

Can Adobe please confirm whether this is an acceptable workaround or not?