Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Adobe Flex SDK Previous
-
None
-
None
-
Affected OS(s): Windows
Affected OS(s): Windows XP
Browser: Other (specify version)
Language Found: English
Description
Steps to reproduce:
1. Using Flex, create an AIR application with NativeApplication.nativeApplication.autoExit = false;
1a. Add in a few standard controls, such as anything with a scrollbar, some text input fields, buttons etc.
2. Create a function to close the window and open a new one eg: call currentNativeWindow.close();
3. At some point later, create a new native window, eg: something like
var w:Window = new Window();
_currentWindow = w;
w.width = player.width;
w.height = player.height;
w.type = NativeWindowType.NORMAL;
w.systemChrome = NativeWindowSystemChrome.NONE;
w.transparent = true;
w.maximizable = false;
w.minimizable = false;
w.resizable = false;
w.showGripper = false;
w.showStatusBar = false;
w.showTitleBar = false;
w.addChild(player);
3. Note how various controls no longer work..
Actual Results:
Tab no longer navigates correctly between fields - in both Flex 3 and Flex 4, focus rectangles are drawn, but focus doesn't change. Scrollbars no longer drag on mouse move. Various other irritations...
Expected Results:
Controls should work correctly.
Workaround (if any):
For homecooked controls, simply directly referencing .stage rather than getSandboxRoot will allow proper mouse and keyboard actions.