On Sun, 10 Jun 2007, Maciej Stachowiak wrote:
> On Jun 8, 2007, at 6:05 PM, Ian Hickson wrote:
> >
> > > I am not an expert here, but IIRC, the underlying PDF/Quartz imaging
> > > model does not allow general xoring. I think it is important to
> > > ensure that canvas can be implemented on top a
On Fri, 8 Jun 2007, Michel Fortin wrote:
> >
> > I don't disagree. Should we just drop these spaces on the floor? It
> > doesn't seem like the best thing but I guess I'm not opposed. What do
> > other people think?
>
> I'd agree they're mostly useless in a browser context, but when reading
> HT
On Jun 8, 2007, at 6:05 PM, Ian Hickson wrote:
I am not an expert here, but IIRC, the underlying PDF/Quartz
imaging model
does not allow general xoring. I think it is important to ensure
that canvas
can be implemented on top a Quartz 2D drawing context on OS X
without breaking
hardware
On Jun 10, 2007, at 15:31, Michel Fortin wrote:
Le 2007-06-10 à 7:05, Anne van Kesteren a écrit :
On Sat, 09 Jun 2007 23:03:54 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I don't think XML does that, actually.
See the first paragraph of http://www.w3.org/TR/xml/#syntax for
the reason
Le 2007-06-10 à 7:05, Anne van Kesteren a écrit :
On Sat, 09 Jun 2007 23:03:54 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I don't think XML does that, actually.
See the first paragraph of http://www.w3.org/TR/xml/#syntax for the
reason why this is so. White space outside the the root
On Sat, 09 Jun 2007 23:03:54 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I don't think XML does that, actually.
See the first paragraph of http://www.w3.org/TR/xml/#syntax for the reason
why this is so. White space outside the the root element is markup and not
text.
--
Anne van Kes
Le 2007-06-09 à 5:26, Anne van Kesteren a écrit :
On Sat, 09 Jun 2007 04:49:56 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I'd agree they're mostly useless in a browser context, but when
reading HTML with the intent of reserializing it later, preserving
the whitespace around the documen
, 2007 11:26 AM
To: Michel Fortin; Ian Hickson
Cc: Henri Sivonen; whatwg List
Subject: Re: [whatwg] Still more comments and questions on Web Apps 1.0
On Sat, 09 Jun 2007 04:49:56 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
> I'd agree they're mostly useless in a browser contex
On Sat, 09 Jun 2007 04:49:56 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I'd agree they're mostly useless in a browser context, but when reading
HTML with the intent of reserializing it later, preserving the
whitespace around the document type declaration, the comments and the
root elem
Le 2007-06-08 à 21:05, Ian Hickson a écrit :
8.2.2.1.
"Append that character to the Document node."
Having text nodes outside the root elements is at least a bit
surprising if
nothing else.
I don't disagree. Should we just drop these spaces on the floor? It
doesn't seem like the best thing
On Mon, 20 Mar 2006, Henri Sivonen wrote:
>
> 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.
Done.
> 5.1.1.
> "(Updating the default* DOM attributes causes content att
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
12 matches
Mail list logo
