Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8039001

[macosx] Textfields in dialogs are disabled after using F3 on Mac OS X to select a window

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: P4 P4
    • tbd
    • 7u6, 8
    • client-libs

      FULL PRODUCT VERSION :
      1.8.0-ea build 132
      The same happens on 1.7.0_51

      ADDITIONAL OS VERSION INFORMATION :
      10.9.1

      A DESCRIPTION OF THE PROBLEM :
      I have a dialog open and I'm typing text in a text field.
      Then I press F3 and mouse-click another window.
      I press F3 again and mouse click my app again.
      The text field in my dialog is now disabled.


      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      I would just run my simple program

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      I would expect textfields to remain enabled.
      ACTUAL -
      Text fields are disabled.

      REPRODUCIBILITY :
      This bug can be reproduced always.

      ---------- BEGIN SOURCE ----------
         public static void main(String[] args) throws Exception
         {
            JFrame f = new JFrame("The mother frame");
            f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            f.setSize(350, 150);
            f.setVisible(true);
            f.setLocationRelativeTo(null);
            JDialog d = new JDialog(f, "Press F3, mouseclick another window, press F3, mouseclick this.");
            d.setModal(true);
            JTextField t = new JTextField("After the F3+clickanother+F3+clickthis I will be disabled");
            d.getContentPane().add(t);
            d.setSize(300, 100);
            d.setLocationRelativeTo(f);
            d.setVisible(true);
         }

      ---------- END SOURCE ----------

      CUSTOMER SUBMITTED WORKAROUND :
      I can CMD+TAB twice to make it enabled again.

            Unassigned Unassigned
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: