No way to specify what URL a webapps launcher should display when activated

[James Henstridge]

I've only tested this with Firefox, so apologies if it should have been filed against the Firefox extension. The program behind webapps .desktop files seems to come from this package though, so I filed it here.

While working on Unity integration for a website locally, I was testing out locking of the webapp's icon to the launcher:

 1. I opened the site as http://scruffy:$random_port/music/buy/ ("scruffy" is my system's host name)
 2. That page calls Unity.init() to initialise the Unity integration.
 3. I right clicked on the new launcher icon and picked "Lock to Launcher"
 4. I closed the web page
 5. I clicked the launcher icon.

In response, a new web browser window was opened pointing at http://scruffy/. This was surprising for a few reasons:
 * The port number was dropped, so the browser didn't return to my application
 * The root web page of my application did not implement integration. In fact, I had never navigated to that page with Unity integration enabled.

I understand that the first page on the site that enables Unity integration might not be the best target for the launcher icon, but the current behaviour seems broken.

Perhaps a scheme like the following might be a better way to determine the URL:

 1. Add an optional "root" key to the parameters dictionary passed to the Unity.init() method. This key would contain the root URL of the web application, which must match the "same origin" constraint as the calling page.
 2. If the "root" key is not present, it should default to the URL "/" relative to the calling page.

That sounds like it should be compatible with current behaviour (other than the current bugs w.r.t. port numbers) while allowing web apps to to use alternative root URLs.

[James Henstridge (jamesh)]

On IRC it was pointed out that I completely missed the section of the documentation where it says how to set the home page for the application.

The other half of the problem still seems real: when I don't manually set the home page, the method used to select a default one seems to be a bit buggy.