Darin Fisher wrote:
Well, there must be some API somewhere to get the right context parameter to pass to necko, right?
There ought to be by the time we're done with 1.9, yes. ;)
Yes, good point. You'd have to do more than just call NewURI.
Note that I want this in newChannel, not newURI. We create plenty of URI objects with no plans to load them (eg visited link checking).
So, this new API isn't useful unless a consumer knows how to get a context in the first place.
Yes.
Maybe it would help me to understand where that comes from.
"It depends". In the simplest setup, the context is the nsIPrincipal that should be used for the security check. Where this comes from depends on the details of what's being loaded, where, by whom, etc.
Yes, this is something that I have always envisioned using those flags for. There are plenty of available bits.
OK. I'd been hoping to be able to output a string representing the capability that needs to be enabled to load the URI in some cases, but I guess I can just use bits to express the common cases (allow, deny, chrome only, need universal xpconnect, need universal browser write, need universal browser read)...
-Boris _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
