Hi,
I'd like to propose the following changes to the registerProtocolHandler
spec.
1. Introduce an isRegistered() function.
Currently if a site wants its users to register it as a handler for a given
protocol it has two options:
a) It can call registerProtocolHandler() on page load. (This
On Tue, Apr 19, 2011 at 9:51 AM, Wilhelm Joys Andersen
wilhel...@opera.com wrote:
. . .
After running the lines of script above, typing any of the
following URLs will lead the user to evilsite.tld:
mail.google.com:80/mail/
192.168.1.1:80
. . .
To save ourselves (and our users) from
On Mon, 11 Apr 2011, Justin Uberti wrote:
On Mon, Apr 11, 2011 at 7:09 PM, Ian Hickson i...@hixie.ch wrote:
This has made UDP packets larger than the MTU pretty useless.
So I guess the question is do we want to limit the input to a fixed
value that is the lowest used MTU (576 bytes
On 04/22/11 00:27, Ian Hickson wrote:
and procedures for identifying the stream in SDP (if we continue to
use SDP) - I believe SDP implicitly assumes that all the streams it
describes are RTP streams.
That doesn't seem to be the case, but I could be misinterpreting SDP.
On Tue, 19 Apr 2011 13:33:43 -0400, Ian Hickson i...@hixie.ch wrote:
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
[...]
We'd like to know if we've missed any important schemes
