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

Modal dialog blocking of browser imprecise with introduction of class loader cache

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Won't Fix
    • Affects Version/s: 6u5
    • Fix Version/s: None
    • Component/s: deploy
    • Labels:
      None
    • Subcomponent:
    • CPU:
      generic
    • OS:
      windows

      Description

      With the introduction of the class loader cache in 6618920, the implementation of modal dialogs' blocking of the web browser has become imprecise in some situations. Consider the case where the simple ModalityTest is loaded in two separate browser windows. Since they now share the same class loader and AppContext, it is essentially random which Applet2Manager instance will be picked up during modalityPushed() and therefore random which browser-side plugin instance, and browser window, will be blocked.

      Probably the only technically feasible solution would be to block all browser windows for all plugin instances sharing the same AppContext. It's unclear whether this would be a good solution from the user experience standpoint.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dcherepanov Dmitry Cherepanov
                Reporter:
                kbr Kenneth Russell (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: