Le 20 févr. 2008 à 07:36, Ian Hickson a écrit :
Indeed, I spoke with Mark about this, and he didn't seem especially
convinced that the example was convincing. :-)
http://diveintomark.org/archives/2008/02/19/all-these-years
--
Karl Dubost - W3C
http://www.w3.org/QA/
Be Strict To Be Cool
Hello
I googled, read the list archive and whatwg forum and did not find
anything about this topic; if it should have been discussed before, I
apologize.
Reading the Webforms 2.0 drafts I found that many useful extensions are
made, but the basic control structure remains untouched. IMO
On Sun, 11 Nov 2007, Jim Jewett wrote:
Instead worrying about how to spell noreferer, why not meet the need
another way, such as a refer attribute which indicates a string to use
in place of the URL.
a href=www.example.comdefault to using the
current URL/a
a
Hi all,
I was looking at the definition of a valid hashed id reference, and I
noticed some inconsistency. The first sentence says the string must
match the id attribute, but then the last parsing rule says that the
string can match the id or name attributes of the element. If the
On Tue, 16 Nov 2004, Christoph Päper wrote:
*Matthew Raymond* [EMAIL PROTECTED]:
1) The h# elements should be depreciated.
2) The h# elements will have no SEMANTIC meaning when inside a section
header. Their presentation, however, will remain the same.
3) Within an h element, h#
On Wed, 13 Feb 2008, Kornel Lesinski wrote:
That's interesting. In that case attack outlined on Mozilla's list is
even less likely to succeed than I thought. So maybe a less abusive
approach would suffice:
* if ping is cross-domain, always send Referer
* if ping originates from the same
On 20 Feb 2008, at 19:47, Adele Peterson wrote:
I was looking at the definition of a valid hashed id reference, and
I noticed some inconsistency. The first sentence says the string
must match the id attribute, but then the last parsing rule says
that the string can match the id or name
ah, I understand now - that makes sense. thanks!
On Feb 20, 2008, at 1:14 PM, Ian Hickson wrote:
On Wed, 20 Feb 2008, Adele Peterson wrote:
I was looking at the definition of a valid hashed id reference, and I
noticed some inconsistency. The first sentence says the string must
match the id
On Wed, 20 Feb 2008, Adele Peterson wrote:
I was looking at the definition of a valid hashed id reference, and I
noticed some inconsistency. The first sentence says the string must
match the id attribute, but then the last parsing rule says that the
string can match the id or name
On Fri, 19 Nov 2004, Matthew Raymond wrote:
Fine, then if we're doing away with vendor UA interpretations of headers,
let's specifically define them as only having the following semantic meaning:
1) Header elements contain only two kinds of header information: the header
title and
On Sat, 16 Apr 2005, Matthew Thomas wrote:
Ian Hickson wrote:
On Thu, 14 Apr 2005, Anne van Kesteren wrote:
...
qfoo bar and then citeIan/cite said:
blockquote
pWell, I don't want to go into details right now.../p
p... but this looks like a very ugly markup construct.../p
On Wed, Feb 20, 2008 at 3:05 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
If XMLHttpRequest is one of the APIs available on background threads,
does that include its XML parsing/serialization features (responseXML
and the ability to pass a Document as the post data)? If so, then
effectively
Executive summary: no changes made; not much controversy.
On Sat, 21 May 2005, Rimantas Liubertas wrote:
On 5/21/05, Ian Hickson [EMAIL PROTECTED] wrote:
...
Actually Steven Pemberton gave some interesting examples of what look
to me like valid use cases for hr/ in a recent talk of his.
13 matches
Mail list logo
