paulkinlan / webintents Goto Github PK

It would be great if a user could "star" a preferred handler so that they don't keep getting prompted to select an app.

Make sure that the make process will only work if NodeJS and UglifyJS are installed.

Perhaps make a ./configure script.

We make a lot of assumptions in the code about sending data between clients. This is a placeholder bug that can be used to track changes and tests.

Examples should work as soon as they are built - currently examples only work locally.

A compelling use-case is to use this as a way to provide access to the OpenID providers that the user actually uses - remove the nascar effect.

Using the current window<->Iframe<->picker model it is not possible to use this inside a Chrome extension. Create a wrapper that allows us to use SharedWorkers where supported to talk between the services.

__WEBINTENT_DEBUG

Remove it - fix the build process.

Given that the base set of Verbs will be in on this we should clear up the JS etc.

I think this is a typo for the directory.

All examples currently use { "uris": } syntax to pass data, when for mime type data it should be "string uri" || ["string uri"]

We want to make sure that the url for the schema's actually have content.

Error: -bash: ./run.sh: /usr/bin/bash: bad interpreter: No such file or directory

If the browser already supports webintents, don't init the framework (there is no point).

The theory is that client and service providers will have to use the shim until it is supported on all platforms.

The system currently assumes that postMessage passes objects, this is not the case. Firefox can only handle strings, thus it fails to work.

SHARE
SEND
EDIT
VIEW

We extensively use addEventListener which is not supported in IE, work out how to put in a shim to handle attachEvent

Using the current window<->Iframe<->picker model it is not possible to use this inside a Chrome extension. Create a wrapper that allows us to use SharedWorkers where supported to talk between the services.

Currently the examples only work when running them locally (ports) fix this so that they work when live on the web.

We need to set window.intent instead of fire navigator.onAction

If you an include an absolute path as the href of the intent then it doesn't correctly append the path, it just has the domain.

When the incoming data isn't an array setText sets textContent which is wrong.

Create a Chrome extension showing the Share functionality that could be built into browsers.

Some postMessage methods use "*" to target all domains on a window. Ensure that these are locked down so that we don't accidentally leak data.

Chrome seems to have stopped loading iframes (when src is set) that are not in the dom - move execution to after DOM insertion

Otherwise it might leak data outside.