Uploaded image for project: 'Apache Flex'
  1. Apache Flex
  2. FLEX-28760

when clicking on TextInput inside Callout, Callout.focusManager.getFocus() is null

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Later
    • Adobe Flex SDK Previous
    • None
    • None
    • Affected OS(s): All OS Platforms
      Affected OS(s): All OS Platforms
      Language Found: English

    Description

      Steps to reproduce:
      1. Use the following code in a mobile application:
      <s:CalloutButton label="display callout" id="calloutButton">
      <s:calloutLayout>
      <s:VerticalLayout paddingLeft="10" paddingRight="10" paddingTop="10" paddingBottom="10"
      gap="10" horizontalAlign="justify"/>
      </s:calloutLayout>
      <s:Button />
      <s:TextInput width="50" click="trace('focus is now on ' + calloutButton.callout.focusManager.getFocus())"/>
      </s:CalloutButton>
      2. Click on the CalloutButton to activate it
      3. Click in the TextInput

      Actual Results:
      Trace statement shows that the Callout's FocusManager.getFocus() returns null.

      Expected Results:
      FocusManager should show that focus has been switched to the TextInput.

      Workaround (if any):
      None.

      Additional notes:
      Found as part of work on SDK-31638.

      Attachments

        Activity

          adobejira Adobe JIRA added a comment -

          Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-31813
          Original Reporter: tkraikit
          Original Resolution: Fixed
          Discoverability: Medium
          Number of votes: 0
          Regression: Yes
          Reproducibility: Every Time
          Resolved by: jsaracin
          Severity: Incorrectly Functioning
          reporter: tkraikit

          adobejira Adobe JIRA added a comment - Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-31813 Original Reporter: tkraikit Original Resolution: Fixed Discoverability: Medium Number of votes: 0 Regression: Yes Reproducibility: Every Time Resolved by: jsaracin Severity: Incorrectly Functioning reporter: tkraikit
          adobejira Adobe JIRA added a comment -

          created: 2011-10-10 12:31:58.000
          resolved: 2011-10-11 13:12:55.829
          updated: 2011-10-11 13:12:56.000

          adobejira Adobe JIRA added a comment - created: 2011-10-10 12:31:58.000 resolved: 2011-10-11 13:12:55.829 updated: 2011-10-11 13:12:56.000
          adobejira Adobe JIRA added a comment -

          On 2011-10-10 12:48:59.474 tkraikit commented:
          Marking as a regression because this bug is an offshoot of introduction of StageText.
          On 2011-10-10 16:24:24.791 jsaracin commented:
          Adding link to SDK-31812, SDK-31638 – this issue was logged as a result of investigations into these issues
          On 2011-10-11 09:39:43.117 jsaracin commented:
          Per email conversation with Adam:
          This is a limitation of StageText as it stands now. Because StageText doesn't send mouseFocusChange events, we need them to make sure that mouse events get sent before focus events (so the target of the mouse events is determined correctly, etc.). So, when the click is received, we won't have received the focus event necessary to have focusManager.getFocus return the text component.

          In light of fixes being pursued for SDK-31812, recommend this be moved to priority C and deferred.
          On 2011-10-11 13:12:56.049 jsaracin commented:
          IRB – resolving as deferred, priority C.

          adobejira Adobe JIRA added a comment - On 2011-10-10 12:48:59.474 tkraikit commented: Marking as a regression because this bug is an offshoot of introduction of StageText. On 2011-10-10 16:24:24.791 jsaracin commented: Adding link to SDK-31812, SDK-31638 – this issue was logged as a result of investigations into these issues On 2011-10-11 09:39:43.117 jsaracin commented: Per email conversation with Adam: This is a limitation of StageText as it stands now. Because StageText doesn't send mouseFocusChange events, we need them to make sure that mouse events get sent before focus events (so the target of the mouse events is determined correctly, etc.). So, when the click is received, we won't have received the focus event necessary to have focusManager.getFocus return the text component. In light of fixes being pursued for SDK-31812, recommend this be moved to priority C and deferred. On 2011-10-11 13:12:56.049 jsaracin commented: IRB – resolving as deferred, priority C.

          People

            adobejira Adobe JIRA
            adobejira Adobe JIRA
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: