On Thu, 30 May 2013, chris cargile wrote:
>
> there seems to be a limitation that either registerProtocolHanlder()
> takes GET requests but not POST requests
Since you are only ever sent a URL, this seems like the appropriate kind
of request, no?
On Thu, 30 May 2013, chris cargile wrote:
>
> ht
Outlook i suspect (v. pipermail) removed one of my links to the original bug
posting at w3c: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22022.
For convenience, view my email with paragraph breaks at http://ow.ly/lyq8H-
Chris
From: follybeach...@hotmail.com
To: whatwg@lists.whatwg.org
Subject
in case the associated thread of messages for this subject are not referenced
by pipermail via this post's title, I wanted to link to them
here-http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-September/023084.html.
I'm writing to discuss/obtain clarification regarding a post that was int
On Sun, 11 Oct 2009 05:09:56 -0400, Ian Hickson wrote:
On Mon, 5 Oct 2009, Michael A. Puls II wrote:
> >
> > 3. URI to a help page where the site explains how it makes uses of
> > registerProtocolHandler and gives help and support contacts etc.
>
> The UA can already keep track of the page fro
On Mon, 5 Oct 2009, Michael A. Puls II wrote:
> > >
> > > 3. URI to a help page where the site explains how it makes uses of
> > > registerProtocolHandler and gives help and support contacts etc.
> >
> > The UA can already keep track of the page from which the user
> > registered the handler, wh
On Mon, 05 Oct 2009 07:27:08 -0400, Ian Hickson wrote:
On Sat, 19 Sep 2009, Michael A. Puls II wrote:
Currently, registerProtcolHandler works like this:
navigator.registerProtocolHandler("protocol",
"http://example.org/?uri=%s";, "title");
However, this doesn't allow the site to specify
On Sat, 19 Sep 2009, Michael A. Puls II wrote:
>
> Currently, registerProtcolHandler works like this:
>
> navigator.registerProtocolHandler("protocol", "http://example.org/?uri=%s";,
> "title");
>
> However, this doesn't allow the site to specify some useful and
> important information about th
On Tue, 22 Sep 2009 11:46:01 -0400, Anne van Kesteren
wrote:
On Tue, 22 Sep 2009 17:32:59 +0200, Michael A. Puls II
wrote:
On Tue, 22 Sep 2009 09:10:02 -0400, Anne van Kesteren
wrote:
Is this not already known? Or is there no same-origin restriction on
these methods?
Do you mean, is
On Tue, 22 Sep 2009 17:32:59 +0200, Michael A. Puls II
wrote:
On Tue, 22 Sep 2009 09:10:02 -0400, Anne van Kesteren
wrote:
The IRI specification dictates UTF-8 already.
But sites might not follow it.
Then they will need to be updated if they want to work with
registerProtocolHandler an
On Tue, 22 Sep 2009 09:10:02 -0400, Anne van Kesteren
wrote:
On Sat, 19 Sep 2009 13:49:15 +0200, Michael A. Puls II
wrote:
Currently, registerProtcolHandler works like this:
navigator.registerProtocolHandler("protocol",
"http://example.org/?uri=%s";, "title");
However, this doesn't al
On Tue, 22 Sep 2009 09:54:12 -0400, João Eiras wrote:
2. The location of an icon like a favicon.ico file or png etc.
This is actually a real privacy issue. The user agent would periodically
fetch a remove favicon, which discloses the end user's ip.
If you go to a site that uses registe
2. The location of an icon like a favicon.ico file or png etc.
This is actually a real privacy issue. The user agent would periodically fetch
a remove favicon, which discloses the end user's ip.
If any, such favicon would need to be made available offline immediately when
installing the pro
On Sat, 19 Sep 2009 13:49:15 +0200, Michael A. Puls II
wrote:
Currently, registerProtcolHandler works like this:
navigator.registerProtocolHandler("protocol",
"http://example.org/?uri=%s";, "title");
However, this doesn't allow the site to specify some useful and
important information ab
Currently, registerProtcolHandler works like this:
navigator.registerProtocolHandler("protocol",
"http://example.org/?uri=%s";, "title");
However, this doesn't allow the site to specify some useful and important
information about the site like:
1. What encoding the server expects. For exa
14 matches
Mail list logo