On Oct 27, 2006, at 03:17, Anne van Kesteren wrote:
However, other types of programs processing HTML5 using XML tools
would have to be allowed to consider xml:lang in text/html non-
conforming and trashable, because what you suggest violates basic
assumptions that XML processing software is
On Fri, 27 Oct 2006 10:48:06 +0200, Henri Sivonen [EMAIL PROTECTED] wrote:
However, other types of programs processing HTML5 using XML tools
would have to be allowed to consider xml:lang in text/html non-
conforming and trashable, because what you suggest violates basic
assumptions that XML
Dear all,even i think that overlapping cells should not be supported, as it would be an encouragement to table based layouts. The specifications not supporting overlapping cells would encourage developers to use table for tabular data only.
-- {Ro}h(a)[n]_-_[P]{rab}(h)u
foo
bar/
bar/
/foo
How can foo.innerHTML be well-formed here?
--
Anne van Kesteren
http://annevankesteren.nl/
http://www.opera.com/
Ian Hickson wrote:
I think it would be good to require table integrity. Specifically I think
overlapping cells would be a MUST NOT.
That's fine for document conformance, but what about how browsers will
handle it? Is the spec still going to require browsers to render
overlapping cells, or
On Fri, 27 Oct 2006 15:17:16 +0200, Lachlan Hunt
[EMAIL PROTECTED] wrote:
That's fine for document conformance, but what about how browsers will
handle it? Is the spec still going to require browsers to render
overlapping cells, or would it be possible to resolve this difference
between
On Oct 27, 2006, at 16:21, Anne van Kesteren wrote:
On Fri, 27 Oct 2006 15:17:16 +0200, Lachlan Hunt
[EMAIL PROTECTED] wrote:
That's fine for document conformance, but what about how browsers
will handle it? Is the spec still going to require browsers to
render overlapping cells, or would
Anne van Kesteren wrote:
foo
bar/
bar/
/foo
How can foo.innerHTML be well-formed here?
It could be if it were treated as an external parsed entity.
http://www.w3.org/TR/REC-xml/#NT-extParsedEnt
--
Lachlan Hunt
http://lachy.id.au/
Hi,
From: Ian Hickson [EMAIL PROTECTED]
headers= will have a MUST requirement to point to TH elements in the
same table, and will probably only be allowed on TDs. scope= will
probably only be allowed for THs.
In HTML4, as I understand it, TDs can act as both data cells and header
cells if
Hi,
I notice that what was previously the i element is now the x element.
[1]
I realize that x is shorter than span. I don't think it's useful to have
both to work with dfn. I suggest either make span don't work with dfn
or drop x.
I also think x should exclusively represent a
10 matches
Mail list logo