- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 23 Apr 2012 13:17:58 -0700
- To: "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>
- Cc: WWW Style <www-style@w3.org>
On Mon, Apr 23, 2012 at 1:13 PM, Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu> wrote: > (12/04/24 3:39), Tab Atkins Jr. wrote: >> Issue 3: Using the 'integer' type in attr() seems to be invalid in >> places that want <number> >> Closed as Invalid - the definition of the <number> type specifically >> says that a number is "either an <integer>, or ...". > > Well, the spec says "either an integer, or ..." You seem to have no > problem about treating "integer" and "<integer>" as synonyms, but I do > have a problem. Based on my impression, this sentence is talking about > the syntax of a <number>, while whether <integer> is a subtype of > <number> has to do with the semantics. > > So, no, this is not very satisfactory, but given that this amounts to an > editorial issue, this is my last try. The following are my editorial > proposals: What if I just link that line in the number definition to <integer> rather than "integer"? ~TJ
Received on Monday, 23 April 2012 20:18:46 UTC