The default bug view has changed. See this FAQ.

Many unimplemented API functions within Webclient



Core Graveyard
Java APIs to WebShell
17 years ago
5 years ago


(Reporter: Ashu Kulkarni, Assigned: Ashu Kulkarni)


Firefox Tracking Flags

(Not tracked)




17 years ago
There are many API functions within the Webclient Spec that have not yet been
implemented. There needs to be a way for Webclient to inform the API users that
the particular feature is as yet unimplemented.

Comment 1

17 years ago
*** Bug 20659 has been marked as a duplicate of this bug. ***

Comment 2

17 years ago
This is confirmed.
Ever confirmed: true

Comment 3

17 years ago
bug 40330

This checkin mainly does two things:

1. Correctly populates the java.awt.event.MouseEvent subclass with the
  correct modifiers, x, y, and clickCount for the mozilla mouse event.

2. Adds a performance optimization: previously, every mouse event was
  causing a new instance of java.util.Properties to be created.  Now,
  only one Properties instance is created per-page, and it is cleared on
  each mouse event.  

Also, I made the DOMMouseListenerImpl constructor initialize the
refCount to 0.  This allows the object to be correctly deleted.  

M classes_spec/org/mozilla/webclient/test/
M classes_spec/org/mozilla/webclient/wrapper_native/
M src_moz/DOMMouseListenerImpl.cpp
M src_moz/DOMMouseListenerImpl.h
M src_moz/WindowControlImpl.cpp
M src_moz/jni_util.cpp
M src_moz/jni_util.h
M src_moz/jni_util_export.cpp
M src_moz/jni_util_export.h

M classes_spec/org/mozilla/webclient/test/

* Added test code for MouseListener properties: buttons, modifiers, etc.

M classes_spec/org/mozilla/webclient/wrapper_native/

* Added support for mouse modifiers.  Pull values out of the hash table,
  put them in the MouseEvent constructor.

M src_moz/DOMMouseListenerImpl.cpp

* Modified constructors so they initialize all ivars.

* changed usage model of properties object to share the lifetime of the
  DOMMouseListenerImpl instance.  Needed to make use of the new function
  util_ClearPropertiesObject() to do this.  Now we have only one call to
  util_DestroyPropertiesObject(), in the DOMMouseListenerImpl

M src_moz/DOMMouseListenerImpl.h

>     virtual ~DOMMouseListenerImpl();
> protected:
> void JNICALL addMouseEventDataToProperties(nsIDOMEvent *aMouseEvent);

M src_moz/WindowControlImpl.cpp

* Initialize new WebShellInitConext member propertiesClass to nsnull

M src_moz/jni_util.cpp

* Added util_ClearPropertiesObject() an optimization.

* Store the jclass for java/util/Properties in an element in
  WebShellInitContext.  This prevents us from having to do FindClass
  each time a mouse event occurs.

* Added a parameter to util_StoreIntoPropertiesObject.

M src_moz/jni_util.h

* Added propertiesClass to WebShellInitContext

* Added new method ClearPropertiesObject 

* Added new last argument to DestroyPropertiesObject

M src_moz/jni_util_export.cpp
M src_moz/jni_util_export.h

* Added function pointer for util_ClearPropertiesObject.

Comment 4

17 years ago
This bug should be closed now that we have implemented a special Exception class
- UniImplementedException.class that is used to indicate to users that a
particular API feature is as yet not implemented.

Last Resolved: 17 years ago
Resolution: --- → FIXED
Component: Java APIs to WebShell → Java APIs to WebShell
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.