Because the app manager will live in a tab, and we don't want to show a chrome://... URL, we would like to have a devtools:xxx URL (like about:xxx). We would have: - devtools:app-manager - devtools:device - devtools:toolbox

Gavin, what do you think about that?

I don't know what the "app manager" is, or what those other URLs will point to - can I read more about that somewhere? In any case, your own protocol handler seems a bit overkill, and increases the security exposure. Can you just use about: URIs instead?

Comment on attachment 790137 [details] [diff] [review] Patch v0.1 Review of attachment 790137 [details] [diff] [review]: ----------------------------------------------------------------- Like Gavin, I'm not sure I fully understand why we can't use about: for this. Is there overlap with what Dave was looking at in bug 779197? ::: browser/devtools/components/DevtoolsProtocolHandler.js @@ +22,5 @@ > +DevtoolsProtocolHandler.prototype = { > + scheme: SCHEME, > + defaultPort: -1, > + protocolFlags: Ci.nsIProtocolHandler.URI_IS_UI_RESOURCE | > + Ci.nsIProtocolHandler.URI_IS_LOCAL_RESOURCE, Is URI_IS_LOCAL_RESOURCE the right thing to use here? I think unless we explicitly want this to be accessible from web content we should use URI_DANGEROUS_TO_LOAD instead.

"The App Tools team is responsible for creating tools to help developers debug and inspect apps written for Firefox OS. This includes the development of Firefox OS Simulator and tools in Firefox to connect and debug apps running on devices or in simulator instances." Mockups: http://htmlpad.org/app-manager/ So basically, we are building a tool called "App Manager" (not the official name yet). It will be accessible from the Web Developer menu. Clicking on "App Manager" will open a new tab in Firefox with the tool inside. The URL of this tool will be: - chrome://browser/content/devtools/app-manager/projects.xhtml From this tool, we can open a new tab that will list many information about the currently connected device: - chrome://browser/content/devtools/app-manager/device.xhtml And from any of these tools, we can open a DevTools toolbox that is connected to a running app. This toolbox is opened in a new tab as well: - chrome://browser/content/devtools/toolbox-window.xul So we want pretty URLs for these 3 pages. We could use "about:xxx", but the URLs might be confusing. These pages are developer tools. So having urls like "about:app-manager" or "about:device" could be confusing because it's not obvious this is for developers. And maybe in the future we might have an app-manager for users, not for developers. And what if we want to build a tool that is for addons development? How would we call it (about:addons)? That's why I was thinking about these devtools:xxx urls. If it's better to use about:xxx urls, could we imagine a "about:dev:xxx" scheme?

Can we hide the URL bar like we do for about:addons?

(In reply to Joe Walker [:jwalker] from comment #5) > Can we hide the URL bar like we do for about:addons? This feature will apparently disappear. In Australis, afaik, we will not hide the bar.

Gavin, does comment 4 help?

about:dev-foo or about:dev:foo (if that works, not sure the URI parser will be happy) seems fine. The main thing I would like to avoid is another protocol handler.

(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #8) > about:dev-foo or about:dev:foo (if that works, not sure the URI parser will > be happy) seems fine. The main thing I would like to avoid is another > protocol handler. Ok.

Add about:app-manager, which is safer than a new protocol as mentioned in previous comments. Paul checked with the PM team, and we're now more comfortable with about:app-manager instead of about:dev:app-manager. I'll update the App Manager menu item in a separate bug after this change.