Anna Nachesa wrote:
What does it means in practice: "the content you're loading chrome:// from is not accessible to everyone"?
Protocol handler doesn't set the URI_LOADABLE_BY_ANYONE flag and does set the URI_IS_UI_RESOURCE flag.
Two different protocols are probably not feasible at this stage because it will mean that the server-side part will also have to be changed, so the things will be made more complex, not less.
I'm not sure why the server-side has to change; the two protocols could talk to the server in the same exact way...
In any case, I still don't see how this could have possibly worked with Gecko 1.7 in your case.
-Boris _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
