On Mar 17, 2006, at 18:48, fantasai wrote:
Henri Sivonen wrote:
2.4.5.
To set metadata with meta elements, authors must first specify a
profile that defines metadata names, using the profile attribute.
In my opinion, it would be useful to predefine the traditional
names and Dublin Core.
Douglas Crockford wrote:
The JSONRequest does only one thing:
snip
Are you planning to take the excellent advice from I forget who to
change the name? The name XmlHttpRequest sucks because it doesn't
necessarily return XML, and it doesn't have to be over HTTP. Let's not
tie the name of a new
Based on the 2006-02-24 version.
1.14.1.
The style and script elements in XHTML have a potentially anything
goes content model. Would it be appropriate for a conformance checker
to only pass style and script types it knows about (with the proper
content model for each type)?
2.14.1.1.
Gervase Markham wrote:
Douglas Crockford wrote:
The JSONRequest does only one thing:
snip
Are you planning to take the excellent advice from I forget who
to change the name?
That was me. Nice to see I'm quite memorable :-)
The name XmlHttpRequest sucks because it doesn't
necessarily
Hi,
I'm just wondering how you're intending to deal with basefont?
AFAIK, the only browser that supports it these days is IE, but it does
so by breaking the DOM (I could be mistaken, but I think NN4 supported
it too).
Considering that no other modern browser supports it and that IE's DOM
On 3/20/06, Douglas Crockford [EMAIL PROTECTED] wrote:
Or indeed wrote your script before this JSONRequest was invented.
I think I see where you are confused. A pre-JSONRequest JSON application
will be using GET, or POST with a conventional POST body.
What exactly is a conventional POST
If the value has alpha less than 1.0, then the value must instead be
returned in the CSS rgba() functional-notation format: the literal
string rgba (U+0072 U+0067 U+0062 U+0061) followed by a U+0028 LEFT
PARENTHESIS, a base-ten integer in the range 0-255 representing the
red component (using
Based on the 2006-02-24 version.
5.1.1.
I think the spec should suggest shift-return as the key combo for
inserting a line separator to make it even more clear that plain
return should break the block.
5.1.1.
(Updating the default* DOM attributes causes content attributs to be
updated as
On Mon, 20 Mar 2006, Hallvord R M Steen wrote:
Spec doesn't disallow submitting leading zeros for input type=number
values but I know a developer who apparently thinks it should.
Is it against the idea of input type=number to send leading zeros if
the users type them?
The format the user
On Mon, 22 Nov 2004, Matthew Thomas wrote:
If UAs don't already return alternate text of child elements as part of
textContent, I suggest filing bugs on those UAs. I see nothing in the
DOM 3 spec saying they shouldn't, and not to do so seems to breach the
spirit of the HTML spec. But
So one of the HTML5 elements is gauge:
Relevancy: gauge70%/gauge
Unfortunately, the study Google did on Web authors showed that authors
cannot spell the word language, and I see no reason to believe that they
might spell gauge either. Also, I've typoed the word gauge three times
so far in
On 3/21/06, Gervase Markham [EMAIL PROTECTED] wrote:
Chris Holland wrote:
That's where the extra HTTP header would come-in:
X-Allow-Foreign-Hosts: Forcing developers who expose such a service,
to make the conscious choice to expose data to the world, what Jim
refers to as OPT-IN.
I
Ian Hickson wrote:
So one of the HTML5 elements is gauge:
Relevancy: gauge70%/gauge
Unfortunately, the study Google did on Web authors showed that authors
cannot spell the word language, and I see no reason to believe that they
might spell gauge either.
But unlike the almost entirely
On Tue, 21 Mar 2006, Lachlan Hunt wrote:
Ian Hickson wrote:
So one of the HTML5 elements is gauge:
Relevancy: gauge70%/gauge
Unfortunately, the study Google did on Web authors showed that authors
cannot spell the word language, and I see no reason to believe that they
might
On Tue, 21 Mar 2006, fantasai wrote:
Ian Hickson wrote:
In all of these cases, there are at most three segments: low, medium,
and high, and in fact in all cases you could get away with having at
most two segments (i.e. just having a low or high marker).
mmm, I've seen a *lot* of
15 matches
Mail list logo
