Uploaded image for project: 'MyFaces Trinidad'
  1. MyFaces Trinidad
  2. TRINIDAD-952

In IE, cursor does not return to the correct component after PPR

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 1.0.7-core, 1.2.7-core
    • Components
    • None
    • IE6 or IE7 browser

    Description

      1) Test cases #1
      TabFails.jspx
      <af:inputText label="Label 1"
      id="inputText1"
      binding="#

      {tabfails.inputText1}

      "
      autoSubmit="true"
      valueChangeListener="#

      {tabfails.doSomething1}

      "/>
      <af:inputText label="Label 2"
      id="inputText2"
      binding="#

      {tabfails.inputText2}

      "
      autoSubmit="true"/>
      <af:inputText label="Label 3"
      id="inputText3"
      binding="#

      {tabfails.inputText3}

      "
      autoSubmit="true"
      partialTriggers="inputText1"/>

      TabFails.java
      public void doSomething1(ValueChangeEvent valueChangeEvent)

      { String value1 = inputText1.getValue() == null ? null : inputText1.getValue().toString(); String value2 = inputText2.getValue() == null ? null : inputText2.getValue().toString(); inputText3.setSubmittedValue(null); inputText3.setValue(value1 + value2); }

      To reproduce the problem, click on inputText1 and modify its value then tab off. In FireFox, the value in InputText3 is updated and the cursor goes to InputText2 (as expected). In IE, the inputText3 is updated but the cursor goes back to inputText1.

      2) Test case #2.
      <af:inputText label="Label 4" autoSubmit="true" binding="#

      {tabfails.inputText4}

      " simple="true"/>
      <af:inputText label="Label 5" autoSubmit="true" binding="#

      {tabfails.inputText5}

      " simple="true"/>
      <af:inputText label="Label 6" autoSubmit="true" binding="#

      {tabfails.inputText6}

      " simple="true"/>

      To reproduce the problem, click on inputText4 and modify its value then tab off. In FireFox, the value in InputText4 is updated and the cursor goes to InputText5 (as expected). In IE, the inputText4 is updated but the cursor goes back to inputText4.

      Both cases involve PPR and the javascript to restore the active element in IE.

      Attachments

        1. Trinidad11_952.patch
          1 kB
          Yee-Wah Lee
        2. Trinidad12_952.patch
          1 kB
          Yee-Wah Lee

        Issue Links

          Activity

            People

              matzew Matthias Wessendorf
              yeelee Yee-Wah Lee
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 5h
                  5h
                  Remaining:
                  Remaining Estimate - 5h
                  5h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified