John Nason wrote: > Hi All, > I am working on a gui test tool with support for Mozilla/Netscape. As of > Mozilla 1.0 I've encountered strange behavior with dialogs created from > javascript. When I go to investigate the object model(drilling down and > inspecting nsIDOMNodes) to record actions it is not quite right... The > easiest way to demonstrate this is to open an instance of DomInspector and > get a js dialog open in the browser. In domInsp. "find window" and point to > "java script application". You will notice that the hierarchy that shows up > is something along the lines of: > dialog > --script > --hbox > ----hbox (etc.) > ----hbox (etc.) (contains dialog-content-box stuff) > --seperator > --script > Notice that the dialog-button-box stuff is missing(OK button, Cancel, etc)? > Now minimize the dialog icon and expand it again. Voila! Hierarchys changed. > Now: > dialog > --xul:vbox (contains dialog-content-box stuff) > --xul:hbox (this is all the dialog-button-box stuff) > ----xulbutton (etc.) > > Problem is when I am drilling through the hierarchy in my code there is no > way to get to the "modified" version that I can figure out. This obviously > appears to be a mozilla XPCOM bug but I need some type of workaround to > support dialog buttons. I just don't have the slighteset idea what is > happening there internally that might cause the object model to change from > a bad state to a good state. Anyone have any ideas whats happening here, > possible workarounds, etc? > I know this is a vague, strange problem but it is important. Thanks for any > input. > -john > >
i do not follow how this is a xpcom problem. have you try the dom or xul newsgroups? doug turner [EMAIL PROTECTED]
