On Fri, 15 Jun 2007 03:05:05 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
On Sun, 5 Nov 2006, �istein E. Andersen wrote:
From section 9.2.3.1. Tokenising entities:
For some entities, UAs require a semicolon, for others they don't.
This applies to IE.
FWIW, the entities not requiring a
Aside: I know that it can be changed but iuml is a very unfortunate name
for i tréma. How about deprecating iuml in favor of itrema?
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon Pieters
Sent: Friday, June 15, 2007 8:49 AM
To: Ian Hickson;
The URI reference http://www.w3.org/TR/REC-html40/references.html in the
HTML 4 refers to RFC 2396 http://www.ietf.org/rfc/rfc2396.txt which is
obsolete by RFC 3986 http://www.ietf.org/rfc/rfc3986.txt . The latter
document has a new section 2.5: Identifying Data, containing the following
new
On Fri, 15 Jun 2007 02:05:05 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
I've defined the parsing and conformance requirements in a way that
matches IE. As a side-effect, this has made things like naiumlve
actually conforming. I don't know if we want this.
Rather not. This would break
On Fri, 15 Jun 2007 20:32:45 +0200, Kornel Lesinski [EMAIL PROTECTED]
wrote:
On Fri, 15 Jun 2007 02:05:05 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
I've defined the parsing and conformance requirements in a way that
matches IE. As a side-effect, this has made things like naiumlve
actually
Once upon a time Ian Hickson shaped the electrons to say...
I've defined the parsing and conformance requirements in a way that
matches IE. As a side-effect, this has made things like naiumlve
actually conforming. I don't know if we want this. On the one hand, it's
pragmatic (after all, why
Some minor comments from looking again at the ImageData section:
Colour spaces are not dealt with at all, but are particularly relevant
for getImageData (else you have no idea what the values mean). It's
probably easiest if no conversions happen at all in the canvas, so you
could have:
