On Tue, 25 Apr 2006, Henri Sivonen wrote:
>
> > I don't want to change the spec to say that you can do whatever you
> > want when handling a parse error, because that is what would cause
> > non-interoperable behaviour.
>
> I see, but I expect people to use TagSoup anyway for non-browser apps..
On Tue, 25 Apr 2006, Henri Sivonen wrote:
>
> The party line has been that the embed element is badly designed and
> evil and needs to be replaced with the object element.
I'll look at your post in more detail at some future point but just as a
heads-up, my current thinking is to include in HTM
(Again, from the document conformance point of view:)
I assume number formats in attributes consistently do not allow
whitespace before and after. Am I right?
I assume that an explicit + sign is always forbidden. Correct?
Is the - sign forbidden in front of zero? (Would be logical
consider
On Apr 15, 2006, at 00:21, Ian Hickson wrote:
On Fri, 14 Apr 2006, Henri Sivonen wrote:
Therefore, I suggest calling apps that have the following properties
conforming with some qualifications:
* The UA is a conforming XHTML5 UA.
* The UA is able to convert any conforming HTML5 document into
On Apr 17, 2006, at 19:14, Henri Sivonen wrote:
Then I found
http://jena.sourceforge.net/tmp/javadoc/com/hp/hpl/jena/iri/
IRIFactory.html
which provides a fascinating number of enforcement options. I could
write a custom datatype wrapper for it, but I don't know which
options to use.
I ha
The party line has been that the embed element is badly designed and
evil and needs to be replaced with the object element.
Yet, for compatibility, tools keep generating embed as a child of
object and practically-oriented guides suggest it. According to
http://weblogs.macromedia.com/accessibi
On Mar 11, 2006, at 02:21, Ian Hickson wrote:
On Wed, 26 Oct 2005, Simon Pieters wrote:
Should "'" be a valid charater reference in text/html? If
not, what
would be correct error handling?
I went with making it valid, since it's valid in XML.
That's problematic, because allowing it as a
On Tue, 25 Apr 2006 00:17:36 +0200, Vladimir Vukicevic
<[EMAIL PROTECTED]> wrote:
Arve's example is how I imagined putPixels working -- basically as a
potential optimization over a bunch of fillRect calls.
Two further clarifications:
1) x and y values for both get/setPixel are both floats.
