I see, the IDNA issue is still unsettled. So do you have advice for how
implementers should parse and validate domain names in the meantime? Should
the implementation convert domain names to punycode, validate their length,
or any of these?
On Mar 21, 2013 7:08 AM, Anne van Kesteren
Why is the replacement encoding called replacement and not x-replacement?
As far as I can tell there is no character set or alias called replacement in
the IANA character
sets list, so accordingly, the replacement encoding should begin with x-, as
in
x-user-defined, also in the Encoding
I believe there should be a DOM attribute that returns the language of a node,
as defined in section 3.2.3.3 The lang and xml:lang attributes.
While there is a lang DOM attribute, it's inadequate because it's only
affected by the element's lang content attribute. Also, I don't see a way to
message for context.)
--Peter
-Original Message-
From: Anne van Kesteren
Sent: Wednesday, April 24, 2013 10:03 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] HTML: A DOM attribute that returns the language of a
node
On Wed, Apr 24, 2013 at 6:49 AM, Peter Occil pocci...@gmail.com
You should report this issue and your previous issue (HTML5 is broken:
menuitem causes infinite loop)
in Bugzilla. The WHATWG HTML spec makes it easy.
--Peter
-Original Message-
From: Michael Day
Sent: Monday, May 13, 2013 10:36 PM
To: wha...@whatwg.org
Subject: [whatwg] Spec
I propose rewriting section 9 and parts of section 10 in a different way, to
use the ABNF format in RFC 5234. (Note that ABNFs are already used in the
current Fetch specification.) With this approach, the definitions for byte
pattern, pattern mask, and the pattern matching algorithm can be
, 2013 2:15 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] An alternative approach to section 9 of Mime Sniffing
On Thu, May 23, 2013 at 7:10 AM, Peter Occil pocci...@gmail.com wrote:
I would appreciate comments.
The only reason Fetch uses ABNF is to match HTTP(-bis) conventions.
It's
Sent: Thursday, May 23, 2013 11:14 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] An alternative approach to section 9 of Mime Sniffing
The pattern matching algorithm is used because certain patterns
require other-than-exact matching. That is why the pattern mask
exists. This is particularly
and informs how the rules for collecting WebVTT cue
timings are written in the WebVTT spec.
--Peter
-Original Message-
From: Anne van Kesteren
Sent: Friday, May 24, 2013 1:28 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] An alternative approach to section 9 of Mime Sniffing
On Thu, May 23
I present this draft of the complete algorithm for parsing a MIME type. I
would appreciate comments.
--Peter
An ASCII alphanumeric is a byte or character in the ranges 0x41-0x5A,
0x61-0x7A, and 0x30-0x39.
A MIME type byte is an ASCII
specifications.)
[1]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22103
[2]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22104
-Original Message-
From: Gordon P. Hemsley
Sent: Saturday, May 25, 2013 3:38 AM
To: Peter Occil
Cc: Anne van Kesteren ; WHATWG
Subject: Re: [whatwg
, return undefined.
--Peter
[1]:
https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p1-messaging.html
-Original Message-
From: Gordon P. Hemsley
Sent: Saturday, May 25, 2013 11:55 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] [mimesniff] Complete MIME type parsing
I noticed two more mistakes.
Change the following:
4. Otherwise, if the current byte is \, increment pointer by 1. Then, if
there is a current byte, append that byte to value.
5. Otherwise, append the current byte to value.
to:
4. If the current byte is \, increment pointer by 1. Then, if
Step 7 of section 4.3 reads:
Let headers be the names of request's author headers, sorted
lexicographically and [[byte lowercased]].
Isn't the phrase byte lowercased rather easy to define, since each author
header can only
contain ASCII characters? Maybe it should be:
7. Let
-
From: Gordon P. Hemsley
Sent: Saturday, May 25, 2013 1:26 PM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] [mimesniff] Complete MIME type parsing algorithm for
section 5
On Sat, May 25, 2013 at 12:46 PM, Peter Occil pocci...@gmail.com wrote:
My algorithm skips only SPACE and TAB instead
The spec for what should happen to that td is the first step of
http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-intr
This case clearly seems like a bug in Gecko: it's treating the math tr
as if it's an HTML tr. That is, it's comparing only the
* Another important point to notice is the fact that this algorithm
allows parameter names to appear without values. This is useful in
situations such as the base64 option in data: URLs that use the mere
presence or absence of a parameter to set its boolean value.
Since you mention data URLs
appears more than once, the answer might be different
depending on the browser.
-Original Message-
From: Gordon P. Hemsley
Sent: Saturday, June 01, 2013 8:25 PM
To: Peter Occil ; whatwg List
Subject: Re: [whatwg] [mimesniff] Review request: Parsing a MIME type
(Re-added the list; I hope
I want to respond to the following issues in the MIME Sniffing spec:
Resources
I suggest the following wording for the issue box starting with A resource
is...
A resource is a data item or message, such as a file or an HTTP response.
I believe this covers the cases that would normally be
Just to clarify:
Are you requesting to have the geo protocol be handled by the browser
itself,
without requiring users to install additional software, and without
requiring
websites to register the protocol in advance?
I assume by out of the box you mean that as soon as you install the
Short of explicitly putting in the HTML namespace at every occurrence of
this, I don't know how to fix this. Putting in the HTML namespace
everywhere is a non-starter, there's something like ten thousand
occurrences of element names in the spec. (Literally. Ten thousand.)
I don't mean in the
One use case I can think of is games. For instance, there are several games
for Android that run the game in a particular orientation, such as Jewels
Deluxe, Shoot the Apple, and similar puzzle and casual games.
I can't speak for why that's the case exactly, but I believe it's for at
least
/public-rdfa-wg/2013May/0064.html
-Original Message-
From: Ian Hickson
Sent: Friday, July 12, 2013 3:48 PM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] HTML: A DOM attribute that returns the language of a
node
On Wed, 24 Apr 2013, Peter Occil wrote:
Well in my case, I have written
/multipage/states-of-the-type-attribute.html#input-impl-notes
-Original Message-
From: Ian Hickson
Sent: Saturday, July 13, 2013 11:39 AM
To: Peter Occil
Cc: WHATWG
Subject: Re: [whatwg] HTML: A DOM attribute that returns the language of a
node
On Fri, 12 Jul 2013, Peter Occil wrote
To: Peter Occil
Cc: WHATWG
Subject: Re: Namespaces and tag names in the HTML parser
On Wed, 10 Jul 2013, Peter Occil wrote:
Short of explicitly putting in the HTML namespace at every
occurrence of this, I don't know how to fix this. Putting in the HTML
namespace everywhere is a non-starter
,
any ambiguity issues they may have are rather benign in my opinion.
--Peter
-Original Message-
From: Ian Hickson
Sent: Thursday, August 01, 2013 3:36 PM
To: Peter Occil
Cc: WHATWG
Subject: Re: Namespaces and tag names in the HTML parser
On Thu, 1 Aug 2013, Peter Occil wrote:
Many
namespace, making confusion much less likely.
--Peter
-Original Message-
From: Ian Hickson
Sent: Thursday, August 01, 2013 4:41 PM
To: Peter Occil
Cc: WHATWG
Subject: Re: Namespaces and tag names in the HTML parser
On Thu, 1 Aug 2013, Peter Occil wrote:
Sec. 12.2.4 (Tokenization
On Tue, Aug 20, 2013 at 3:28 PM, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
IMHO, the example that Philip provided in http://people.opera.com/~**
philipj/click.html http://people.opera.com/~philipj/click.html is not a
realistic example of something a JS dev would do.
I'm afraid this
Apparently, the use cases I mentioned before have not been discussed yet:
- Localization of form controls in languages where browser support
is lacking, such as some minor languages.
- Localization of HTML elements, especially date formatting of span
and div elements in the page's default
29 matches
Mail list logo
