Re: Protocol handler flags for custom protocols that use themselves as UI resources

2016-01-25 Thread Cameron Kaiser
On 1/25/16 9:49 PM, Boris Zbarsky wrote: On 1/26/16 12:42 AM, Cameron Kaiser wrote: Currently, it sets ALLOWS_PROXY | ALLOWS_PROXY_HTTP | URI_IS_LOADABLE_BY_ANYONE | URI_IS_UI_RESOURCE. Those last two flags are defined to be mutually exclusive; setting both has undefined behavior in the sense

Re: Protocol handler flags for custom protocols that use themselves as UI resources

2016-01-25 Thread Cameron Kaiser
On 1/25/16 9:49 PM, Boris Zbarsky wrote: On 1/26/16 12:42 AM, Cameron Kaiser wrote: Currently, it sets ALLOWS_PROXY | ALLOWS_PROXY_HTTP | URI_IS_LOADABLE_BY_ANYONE | URI_IS_UI_RESOURCE. Those last two flags are defined to be mutually exclusive; setting both has undefined behavior in the sense

Re: Protocol handler flags for custom protocols that use themselves as UI resources

2016-01-25 Thread Boris Zbarsky
On 1/26/16 12:42 AM, Cameron Kaiser wrote: Currently, it sets ALLOWS_PROXY | ALLOWS_PROXY_HTTP | URI_IS_LOADABLE_BY_ANYONE | URI_IS_UI_RESOURCE. Those last two flags are defined to be mutually exclusive; setting both has undefined behavior in the sense that code will and does assume they are

Protocol handler flags for custom protocols that use themselves as UI resources

2016-01-25 Thread Cameron Kaiser
OverbiteFF (a Gopher add-on for Firefox) calls itself for certain internal resources. Since it converts gopher menus to HTML, it just does things like gopher:///internal.js";> to access its built-in content resources. This worked fine until Firefox 44, which throws a Security Error, so I