- From: Joseph A Holsten <joseph@josephholsten.com>
- Date: Tue, 27 Jan 2009 08:41:02 -0600
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, HTML WG <public-html@w3.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 27, 2009, at 7:38 AM, Julian Reschke wrote:
> Lachlan Hunt wrote:
>> ...
>> "If the application may use a document of MIME type 'text/html' and
>> character encoding 'UTF-8', about:blank SHOULD be represented with
>> an empty document."
>> I suggest you use the phrasing from my draft and add a reference
>> to HTML5.
>
> That will make it hard to publish the spec before HTML5, unless the
> reference is informative (is it?).
>
> > ...
>> Julian Reschke wrote:
>>> - "abouturi = "about:" segment" - restricting to segment sounds
>>> good,
>>> but does this reflect reality?
>> Looking at the syntax from RFC 3986:
>> segment = *pchar
>> pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
>> unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
>> pct-encoded = "%" HEXDIG HEXDIG
>> sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
>> / "*" / "+" / "," / ";" / "="
>> That doesn't look right. Mozilla uses a query string for some
>> [3], which isn't permitted by that syntax.
>> I'm not sure about supporting percent encoding. Testing with the
>> URI about:confi%67, these are the results:
>> Opera: The address bar changes to "opera:config", but still returns
>> an error.
>> Firefox: Says the URL is not valid.
>
> If "about" is to be considered to be an URI scheme, these are bugs.
+1 but sadly, until this is published, these are just as informally
specified features as everything else. Anyone else got an opinion?
http://josephholsten.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkl/HP4ACgkQrPgSa0qMrmE8EACdHNvoz7470uKhDpdegC3ASPyZ
evcAnRePwZHxa/otcfm/IloSg2KQ0Mw+
=0gK8
-----END PGP SIGNATURE-----
Received on Tuesday, 27 January 2009 14:41:56 UTC