Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      411

      Description

      The methods isSynchronize, getInstanceNum, getNativeWindow, as i know, are only important for
      WebBrowser class. Now with WebKitWebBrowser, issue #409 with JEditorPaneWebBrowser and issue
      #410 with WebBrowserBean there are three implementations that don't need this methods, versus one
      that need it.

      The methods only needed in NativeEventThread, and i think there would never be a second
      implementation of WebBrowser, so we can refer to WebBrowser in NativeEventThread instate of
      IWebBrowser.
      Another solution would be a MozIeWebBrowser interface which extends IWebBrowser and add this
      methods and use it in WebBrowser and NativeEventThread.

      I'm also not sure if we real need setInitFailureMessage, getInitFailureMessage, setInitialized and
      isInitialized.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            michael_shan
            Reporter:
            lordy
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: