Anna Nachesa wrote:
Linking to chrome:// from web-accessible content is wrong. There is no
problem linking to .xul per se.
Well, strictly speaking this content is not web-accessible. This is a page
generated locally, by the application itself. It doesn't come from the
server.
I thought you said your xxx protocol was linkable to from file://? That
means that web content can also link to it.
Anyway, I guess I either have to change the content so that it doesn't
lilnks to chrome or to tweak SecurityManager so that it doesn't restrict our
protocol. I would prefer the first option.
Yes, the first option is the way to go.
-Boris
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
