[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi
[ https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688006#comment-13688006 ] Shigeru Nakagaki commented on FLEX-29002: - At the first, compiler.accessible option have to be false. And a screen reader like Microsoft Narrator should be installed and enabled. In this case, Capabilities.hasAccessibility and Accessibility.active are both true. "compiler.accessible = false" makes displayObject.accessibilityProperties null, I guess. PopUpManagerImpl/handleAccessibilityForNestedPopups() does not check displayObject.accessibilityProperties is null or not. So a RTE happens. > RunTime Error #1009 at > mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying > more than one modal popup via PopUpManager on top of each other. On Windows 7 > running on some PCs > --- > > Key: FLEX-29002 > URL: https://issues.apache.org/jira/browse/FLEX-29002 > Project: Apache Flex > Issue Type: Bug > Components: PopUp Manager >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0 > > Attachments: ScreenReaderOnAccessibleOffTest.zip > > > Steps to reproduce: > 1. in the AIR application, create modal popup via popupmanager -> ok. > 2. on the popup, create another modal popup via popupmanager (so we have two > modal popups one on top of the other) -> RT error #1009. > 3. close top popup, due to RT error #1009 modal shade stays on stage and > keeps blocking the application. > > Actual Results: > Popupmanager closes modal titlewindow, but the modal shade stays on display > due to RunTime error #1009 and so application becomes non-operable. > > Expected Results: > Popupmanager should close the modal titlewindow along with the modal shade > as it does if only one modal popup was invoked. > > Workaround (if any): > On Windows7 Control Panel, disable some stuff in control panel (Attachments) > and reboot OS. Trully, this works. > > Note: > This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI > AE2050). Bug is connected with the accessibility OS provides, so we can fix > the issue by configuring some OS parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi
[ https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687563#comment-13687563 ] Shigeru Nakagaki commented on FLEX-29002: - Please do not forget to set accessible = false on compiler setting. (My attached project includes it in .actionScriptProperties) > RunTime Error #1009 at > mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying > more than one modal popup via PopUpManager on top of each other. On Windows 7 > running on some PCs > --- > > Key: FLEX-29002 > URL: https://issues.apache.org/jira/browse/FLEX-29002 > Project: Apache Flex > Issue Type: Bug > Components: PopUp Manager >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0 > > Attachments: ScreenReaderOnAccessibleOffTest.zip > > > Steps to reproduce: > 1. in the AIR application, create modal popup via popupmanager -> ok. > 2. on the popup, create another modal popup via popupmanager (so we have two > modal popups one on top of the other) -> RT error #1009. > 3. close top popup, due to RT error #1009 modal shade stays on stage and > keeps blocking the application. > > Actual Results: > Popupmanager closes modal titlewindow, but the modal shade stays on display > due to RunTime error #1009 and so application becomes non-operable. > > Expected Results: > Popupmanager should close the modal titlewindow along with the modal shade > as it does if only one modal popup was invoked. > > Workaround (if any): > On Windows7 Control Panel, disable some stuff in control panel (Attachments) > and reboot OS. Trully, this works. > > Note: > This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI > AE2050). Bug is connected with the accessibility OS provides, so we can fix > the issue by configuring some OS parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wind
[ https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shigeru Nakagaki updated FLEX-29002: Attachment: ScreenReaderOnAccessibleOffTest.zip 1. Turn on the Microsoft Narrator from control panel on Windows 7 2. Execute the attached ScreenReaderOnAccessibleOffTest.mxml 3. click show PopUp button 4. click show alert button 5. click OK button then, you will get a following exception TypeError: Error #1009: Cannot access a property or method of a null object reference. at mx.managers::PopUpManagerImpl/handleAccessibilityForNestedPopups()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1541] at mx.managers::PopUpManagerImpl/removeModalPopUpAccessibility()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1482] at mx.managers::PopUpManagerImpl/popupRemovedHandler()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1230] at flash.display::DisplayObjectContainer/removeChild() at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::rawChildren_removeChild()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/SystemManager.as:2152] at mx.managers::SystemManager/removeChild()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/SystemManager.as:1795] at mx.managers::PopUpManagerImpl/removePopUp()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:641] at mx.managers::PopUpManager$/removePopUp()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManager.as:238] at mx.controls.alertClasses::AlertForm/removeAlert()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/alertClasses/AlertForm.as:532] at mx.controls.alertClasses::AlertForm/clickHandler()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/mx/src/mx/controls/alertClasses/AlertForm.as:571] On Windows 8 note PC, The Capabilities.hasAccessibility && Accessibility.active are both true even if Microsoft Narrator is OFF. I do not know why. The AIR runtime is 3.5.0.1060 on my test environment. thanks > RunTime Error #1009 at > mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying > more than one modal popup via PopUpManager on top of each other. On Windows 7 > running on some PCs > --- > > Key: FLEX-29002 > URL: https://issues.apache.org/jira/browse/FLEX-29002 > Project: Apache Flex > Issue Type: Bug > Components: PopUp Manager >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA > Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0 > > Attachments: ScreenReaderOnAccessibleOffTest.zip > > > Steps to reproduce: > 1. in the AIR application, create modal popup via popupmanager -> ok. > 2. on the popup, create another modal popup via popupmanager (so we have two > modal popups one on top of the other) -> RT error #1009. > 3. close top popup, due to RT error #1009 modal shade stays on stage and > keeps blocking the application. > > Actual Results: > Popupmanager closes modal titlewindow, but the modal shade stays on display > due to RunTime error #1009 and so application becomes non-operable. > > Expected Results: > Popupmanager should close the modal titlewindow along with the modal shade > as it does if only one modal popup was invoked. > > Workaround (if any): > On Windows7 Control Panel, disable some stuff in control panel (Attachments) > and reboot OS. Trully, this works. > > Note: > This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI > AE2050). Bug is connected with the accessibility OS provides, so we can fix > the issue by configuring some OS parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi
[ https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686485#comment-13686485 ] Shigeru Nakagaki commented on FLEX-29002: - This still happens if compiler.accessible = false and a screen reader was installed, when a modal popUp like mx:Alert is closed. TypeError: Error #1009: Cannot access a property or method of a null object reference. at mx.managers::PopUpManagerImpl/handleAccessibilityForNestedPopups()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1541] at mx.managers::PopUpManagerImpl/removeModalPopUpAccessibility()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1482] at mx.managers::PopUpManagerImpl/popupRemovedHandler()[/Users/justinmclean/Documents/ApacheFlexSDK/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as:1230] at flash.display::DisplayObjectContainer/removeChild() > RunTime Error #1009 at > mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying > more than one modal popup via PopUpManager on top of each other. On Windows 7 > running on some PCs > --- > > Key: FLEX-29002 > URL: https://issues.apache.org/jira/browse/FLEX-29002 > Project: Apache Flex > Issue Type: Bug > Components: PopUp Manager >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA >Assignee: Carol Frampton > Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0 > > > Steps to reproduce: > 1. in the AIR application, create modal popup via popupmanager -> ok. > 2. on the popup, create another modal popup via popupmanager (so we have two > modal popups one on top of the other) -> RT error #1009. > 3. close top popup, due to RT error #1009 modal shade stays on stage and > keeps blocking the application. > > Actual Results: > Popupmanager closes modal titlewindow, but the modal shade stays on display > due to RunTime error #1009 and so application becomes non-operable. > > Expected Results: > Popupmanager should close the modal titlewindow along with the modal shade > as it does if only one modal popup was invoked. > > Workaround (if any): > On Windows7 Control Panel, disable some stuff in control panel (Attachments) > and reboot OS. Trully, this works. > > Note: > This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI > AE2050). Bug is connected with the accessibility OS provides, so we can fix > the issue by configuring some OS parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-29002) RunTime Error #1009 at mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying more than one modal popup via PopUpManager on top of each other. On Wi
[ https://issues.apache.org/jira/browse/FLEX-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686488#comment-13686488 ] Shigeru Nakagaki commented on FLEX-29002: - Also, on Windows 8 note PC and compiler.accessible = false, this always happens. > RunTime Error #1009 at > mx.managers::PopUpManagerImpl/addModalPopUpAccessibility() when displaying > more than one modal popup via PopUpManager on top of each other. On Windows 7 > running on some PCs > --- > > Key: FLEX-29002 > URL: https://issues.apache.org/jira/browse/FLEX-29002 > Project: Apache Flex > Issue Type: Bug > Components: PopUp Manager >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): Windows > Affected OS(s): Windows 7 > Language Found: English >Reporter: Adobe JIRA >Assignee: Carol Frampton > Fix For: Adobe Flex SDK Next, Apache Flex 4.10.0 > > > Steps to reproduce: > 1. in the AIR application, create modal popup via popupmanager -> ok. > 2. on the popup, create another modal popup via popupmanager (so we have two > modal popups one on top of the other) -> RT error #1009. > 3. close top popup, due to RT error #1009 modal shade stays on stage and > keeps blocking the application. > > Actual Results: > Popupmanager closes modal titlewindow, but the modal shade stays on display > due to RunTime error #1009 and so application becomes non-operable. > > Expected Results: > Popupmanager should close the modal titlewindow along with the modal shade > as it does if only one modal popup was invoked. > > Workaround (if any): > On Windows7 Control Panel, disable some stuff in control panel (Attachments) > and reboot OS. Trully, this works. > > Note: > This happens only on Windows 7 OS running on some All-In-One PCs (eg.: MSI > AE2050). Bug is connected with the accessibility OS provides, so we can fix > the issue by configuring some OS parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FLEX-33423) We can input text over than maxChars when we use "Insert" mode.
Shigeru Nakagaki created FLEX-33423: --- Summary: We can input text over than maxChars when we use "Insert" mode. Key: FLEX-33423 URL: https://issues.apache.org/jira/browse/FLEX-33423 Project: Apache Flex Issue Type: Bug Components: Spark: TextInput Affects Versions: Apache Flex 4.9.0 Environment: Windows 7 64bit Japanese Apache Flex SDK 4.9.1 AIR SDK 3.5 Reporter: Shigeru Nakagaki If maxChars is 6, usually we can not input 7 chars. However, when you set "Insert" mode, we can input 7 chars. In mx:TextInput which uses flash.text.TextField class, this does not happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira