Here's a solution that's still a bit ugly but at least a little less drastic
than commenting out parts of Dojo... Override dojo.dom.isNode in your code
as follows:
dojo.dom.isNode=function(wh){
if(typeof Element=="function"){
try{
//return wh instanceof Element;
return Object.isEl
I just run into the same exact thing, using Tap 4.1.5, dojo that comes with
it, propertyselection and an eventlistener as well as prototype. Anybody
know if this is fixed in a newer snapshot, if there is a bug open on this or
any (better) workaround?
Kalle
On Sat, Oct 27, 2007 at 9:41 AM, lt <[EM
Ok after looking into this. It appears to be a conflict with DOJO and
Prototypte. the isNode method in dojo check to see if Element is of type
function and then compare it to the object. I am not willing to give up
prototype for this, so i just commented out this section of the code in
/dojo-0.4
when i changed the initialization from @InitialValues to finishLoad(...) it
started working. It really is amazingly simple to make this kind of
functionality with EventListener.
On 9/19/06, Jani Lindqvist <[EMAIL PROTECTED]> wrote:
Hello,
should the model of component B be persisted or set a
This brings a question: what is the proper strategy to initialize property
values when using ajax submits? Does finishLoad() does the trick? I am still
a bit confused about when all those methods/listeners are invoked and in
which order
I've got a question about this as well, although I am Tap
Hello,
should the model of component B be persisted or set as property?
I have a page that has the same logic as in this example, but the
dynamically populated combobox value is always null when the post is done
(and also in the eventlistener method).
If i change the model to be fetch from a ge
Ok thanks Jesse
I think I figured out what the problem was. My model values were initialized
in the pageBeginRender listener, thus resetting the model value I had just
modified in the event listener. After I switched to @InitialValue
annotations instead, it worked.
This brings a question: what is
I'm not sure. Something sounds wrong. How does the work when not using ajax?
I mean, are you sure you are hitting problems related to dynamic behavior or
more with dealing with normal api semantics?
The debug should explicitly show you the content it is updating a component
with. If it has debug
debug statement says it has updated the content of the component, but the
options are still the old ones.
I also ran the app on debug, and set a breakpoint within the
renderComponent() method in the PropertySelection class. It seems it still
grabs the old value of the model, even after I updated i
It should work, I ~think~...What kind of response do you get from the server
? (via the dojo debug statements or FireBug ? )
On 9/13/06, Christian Dutaret <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to change the content of a dropdown list when some event
occur.
I am using PropertySelection
10 matches
Mail list logo
