Hi, Leonard Ritter wrote:
I am currently working on embedding the mozilla browser in a Python application under Win32, and decided to take the nsIWebBrowser/nsIWebBrowserChrome approach. I noticed that essential functions to get this working are marked as [noscript] in the xpcom interface files, so i took the noscript parts out and recompiled the descriptors, et voila, it is indeed possible.
OK, since the two interfaces you mentioned don't have any noscript stuff, I can't comment on why it might be there.
However, noscript does not mean "JavaScript in webpages should not access this". In very few cases this is the purpose. Remember that the user interface of Mozilla and Firefox is written in JavaScript too.
Often, noscript methods are cases where the function does not use normal XPCOM semantics, or uses a type not available outside of C/C++.
However, I do think that noscript is overused and that many cases of it probably shouldn't be noscript.
I believe Java embedding also can't use noscript methods. I would suggest filing bugs on the cases that cause problems for you, maybe there's no good reason for it in those cases and it can be removed.
I guess that it was thought about using python for web pages as well, and therefore noscript was used for python scripts, but that makes no sense:
I don't think anyone has plans for that...
Now what I would like is a standard way to disable noscript blocking for pyxpcom. When embedding a browser on a client system, the restriction makes no sense.
It doesn't seem like a good idea to me to make pyxpcom ignore noscript. Like I said, in some cases it's used where the method doesn't follow XPCOM semantics, so that seems like a crashy route to go.
_______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
