hi boris, i finally find a way to achieve my origin requirement.it behaves like this: i have to implement the nsIWindowCreator and reguarly create a new chrome in it, but i set a flag in the new chrome to mark it will be destroyed once after getting the real url. and i will do this in the nsIURIContentListener::OnStartURIOpen which is implemented in my chrome. is it ok? i have tested serveral times and get nothing wrong .
i think the key step is that i occasionally find the nsIURIContentListener interface and the nsWebbrowser give me a chance to feed it to the gecko for hoping callback. now i eagerly want to know on earth how many interfaces and callback i can use ,on the other word,is there a full list that shows all process-stage in which gecko enable us extention-developers to participate ? execuse me for bothering u again and again.but i know you are so kind~ _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
