Paul Rouleau wrote: > Does mfcembed use a different javascript engine from mozilla's. I > have a javascript intensive web page that is displaying quite > differently in mozilla from what it displays in mfcembed.
The same engine is used in all Mozilla apps and embedding test harnesses. > Can somebody tell be where the javascript engine is hooked up to the > application? > If these two applications are using the same javascript engine, is it > possible that they are configured differently. If so, how do you do > that? You're probably barking up the wrong tree. The differences between Mozilla and mfcembed are in the front ends: Mozilla uses XUL, mfcembed uses MFC. The Gecko and JS engine back ends are pretty much the same, but the FE<=>BE interfaces used are different. It would help if you said more about what is different, showed screenshots, etc. > As for embedding apps, is there a way to see what is in the DOM after > the javascript has been parsed? Does DOM inspector not work in mfcembed, if you use the right chrome: URL to load it? Note followup-to: m.dom, I'm pretty sure that's the best group for now (m.jseng is the wrong group, m.embedding is good for a one-shot call for help). /be
